Skip to main content
Glama

get_nfts

NFTs in the user's EVM wallets on one network. They are not included in the portfolio total (no reliable price).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_nfts"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork (default eth).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that NFTs have no reliable price and are excluded from totals, but says nothing about what happens with spam/airdrop NFTs, whether results can be empty, or whether the call requires an authenticated wallet set.

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?

Two short sentences, front-loaded with what is returned and followed by the pricing caveat. No wasted words, though the phrasing is slightly telegraphic.

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

Completeness4/5

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

For a one-optional-parameter read tool with full schema coverage, the description covers the resource, its scope, and the key caveat about pricing. Lack of output schema means return shape is unexplained, but that is a minor gap at this complexity.

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% and the single chain parameter is fully documented with an enum and default, so the baseline is 3. 'On one network' reinforces the single-chain scoping but adds no syntax or semantics beyond the schema.

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?

States the specific resource (NFTs), the scope (the user's EVM wallets), and the constraint (one network), which is enough to distinguish it from portfolio and asset tools. It also clarifies an implicit relationship by noting NFTs are excluded from the portfolio total.

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

Usage Guidelines3/5

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

The 'not included in the portfolio total' note implies this is the place to look for NFT holdings the portfolio omits, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources