Skip to main content
Glama

My MCP Server

spl-token-metadata-resolver

Live Solana Mainnet spl-token-metadata-resolver ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

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": "spl-token-metadata-resolver"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/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 does disclose two genuinely useful traits — live Mainnet-only data and a paid call requiring an x402 v2 PAYMENT-SIGNATURE header with $0.10 USDC — but says nothing about read-only nature, failure modes for unknown mints, or freshness/latency of the metadata.

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

Conciseness3/5

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

It is a single compact clause with the payment cost front-loaded, so there is no padding. But it is a fragment that spends its only sentence on pricing rather than on the operation, so brevity is not earning its place.

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?

With zero annotations, zero schema coverage, and no output schema, the description must compensate for everything and does not. An agent is left unable to determine the output shape, the role of targetWallet, or whether the call is read-only.

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 description coverage is 0% across two parameters (mint, targetWallet) and the description supplies no meaning for either. Critically, targetWallet is unexplained — an agent cannot tell whether it scopes wallet-specific metadata or is an unrelated filter, making the tool hard to invoke correctly.

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

Purpose2/5

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

The description only restates the tool name ('spl-token-metadata-resolver') and appends pricing details; it never states in prose what resolution means (e.g., fetching on-chain token name/symbol/decimals for a mint). The verb+resource is inferable from the name alone, which is the definition of a tautological description.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no differentiation from any sibling such as rug-pull-mint-auditor or holder-concentration-analyzer. The only added clause is a price, which tells an agent nothing about when this tool is the right choice.

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