Skip to main content
Glama

game_nft_item

Query NFT item details for a given game and token ID. Get information about game-specific NFTs.

Instructions

[Gaming] 游戏NFT查询 — $0.03/call (free tier: 50/50 today) API: https://goldbean-api.xyz/paid/game-nft-item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameYes游戏名
tokenIdYesTokenID(可选)
Behavior1/5

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

No annotations are provided, so the description must carry the full burden. However, it offers no behavioral details: no indication of whether the tool is read-only, what permissions are needed, rate limits, or side effects. The pricing info is present but does not disclose behavioral traits.

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

Conciseness2/5

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

The description is extremely short (two lines) but fails to provide essential information. It is under-specified for a tool with two required parameters and no output schema. Conciseness here sacrifices clarity and completeness.

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?

The tool has no output schema and no annotations, so the description must be comprehensive. It only provides pricing and API URL, leaving the agent completely in the dark about what data is returned, how to interpret results, or any usage context. This is severely inadequate.

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% with descriptions for both parameters (game name and token ID). The description adds no extra meaning beyond the schema; the Chinese parameter descriptions are already in the schema. Baseline 3 is appropriate as the description does not diminish or contradict schema info.

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 states '游戏NFT查询' which is essentially a translation of the tool name 'game_nft_item'. It adds a '[Gaming]' label and pricing info, but fails to specify what exactly the tool does (e.g., query item details, metadata, ownership). It does not distinguish itself from sibling NFT tools like nft_metadata or nft_owner.

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. The description does not mention any use case, prerequisites, or exclusion conditions. The agent receives no help in choosing between this and other NFT-related sibling tools.

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/wuzenghai616-lang/goldbean'

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