Skip to main content
Glama

wallet_get_holdings_page

Retrieve a paginated list of token holdings for a Solana wallet by providing the wallet address and page number.

Instructions

Fetch paginated wallet holdings via Dritan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYes
pageYes
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description merely says 'Fetch', implying read-only. No disclosure of authentication, rate limits, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence that front-loads purpose. However, it is too brief and omits important details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 2 parameters without descriptions, the description is severely incomplete. Lacks info on return format, errors, or behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 0% and description adds no meaning to parameters 'wallet' (format?) or 'page' (range?). Fails to compensate for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Fetch paginated wallet holdings', distinguishing it from sibling tools like wallet_get_holdings (non-paginated). Mention of 'via Dritan' adds a dependency hint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs siblings. Does not mention alternatives or conditions for pagination.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amirdauti/dritan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server