Skip to main content
Glama
Sign In
jorkal-nft-mcp

jorkal-nft-mcp

Official
by jorkal-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nft_token

Retrieve comprehensive details for any Solana NFT using its mint address, including owner, collection, listing price, image, and traits.

Instructions

Get detailed information about a single Solana NFT by its mint address — includes name, owner, collection, current listing price, image URL, and all on-chain attributes/traits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint": "<mint>"
    },
    "name": "nft_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description covers return fields but does not disclose any behavioral traits such as error handling, authentication needs, or potential side effects. For a read-only tool, this is adequate but not comprehensive.

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 effectively communicates purpose and output fields. No unnecessary words or fluff.

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?

Given simple tool (1 param, no output schema), description adequately covers purpose and return fields. Lacks mention of scenario where NFT not found or required permissions, but these are minor gaps.

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?

Parameter 'mint' is described in schema as 'Solana token mint address (base58)'. Tool description repeats that it is 'by its mint address'. No additional meaning beyond schema, so baseline 3.

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 describes the verb 'Get detailed information', resource 'single Solana NFT', and scope 'by its mint address'. The description lists specific data fields (name, owner, collection, etc.), making it distinct from sibling tools like nft_activity or nft_floor.

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

Usage Guidelines4/5

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

Implies use for retrieving full details of a specific NFT. Does not explicitly state when not to use or compare to siblings, but the listed fields make its purpose clear relative to the siblings.

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

Deploy Server

Other Tools