Free PREVIEW of a wallet portfolio snapshot for any public address.
Returns total USD value, number of holdings, and the single largest holding. The FULL
itemized holdings breakdown is available from the paid HTTP endpoint in `full_report`.
chain: e.g. 'base', 'ethereum', 'optimism', 'polygon', 'solana'.
address: a public wallet address (read-only; no keys needed).
| Name | Required | Description | Default |
|---|---|---|---|
| chain | Yes | ||
| address | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses read-only nature, no keys needed, and that only a preview is returned. It could mention potential errors or rate limits, but overall it is transparent about capabilities and limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four concise sentences, front-loaded with purpose and return values, then parameter details. No redundant or missing information; every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and simple parameters, the description covers the essentials. It could clarify the return format (e.g., JSON object) but is otherwise complete for the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains both parameters (chain and address) with examples and notes, significantly adding meaning beyond the bare schema (which has 0% coverage). This fully compensates for the missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it is a 'Free PREVIEW of a wallet portfolio snapshot for any public address' and lists the specific return values (total USD value, number of holdings, largest holding). This distinguishes it from siblings like 'rug_scan_preview' and 'paid_api_info', which are different tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when to use: for a quick free summary. It also provides a clear alternative: 'The FULL itemized holdings breakdown is available from the paid HTTP endpoint in full_report', guiding the agent away from this tool when full data is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: API info, rug scan preview, and wallet report preview. There is no overlap or ambiguity between them.
All names use snake_case and are descriptive, but they do not follow a strict verb_noun pattern (e.g., 'paid_api_info' is adjective_noun_noun). The pattern is mostly consistent.
With only 3 tools, the server feels limited for a crypto domain. It provides basic previews and API info but lacks core trading or data retrieval tools, making the scope narrow.
The tool surface is severely incomplete for a crypto MCP. Missing essential operations like price queries, balance checks, transactions, or trading actions. Only previews and API info are offered.