Skip to main content
Glama

get_nfts_by_owner

Retrieve all NFTs owned by a Solana wallet address. Specify the wallet and optional network to list the NFTs.

Instructions

Get all NFTs owned by a wallet address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_addressYesWallet address
networkNoSolana network
Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose key behaviors like pagination, rate limits, or data freshness. It only states the basic functionality.

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

Conciseness5/5

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

Single sentence, front-loaded with key verb and resource. No unnecessary words; maximizes clarity within minimal space.

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

Completeness2/5

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

Lacks details on return format, pagination, or limits. For a tool that could return many NFTs, the description is incomplete without output schema or behavioral notes.

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

Parameters3/5

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

Schema coverage is 100%, so the description adds no new meaning beyond the parameter names and types. The description does not provide additional context for wallet_address or network.

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

Purpose4/5

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

Description clearly states it retrieves all NFTs owned by a wallet address. Verb and resource are specific, and it distinguishes from sibling tools like get_nft_metadata or get_balance.

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 versus alternatives such as get_nft_collection_info or get_token_accounts. The description does not provide any context for selection.

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/AjithJS99/solana-mcp'

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