DeskCrew - AI Chatbot, Helpdesk & Knowledge base

nft_price

Price, 24h change, liquidity, 24h volume, market cap, pair age and the pair link for any token on Base, Ethereum, Polygon, Avalanche, Sei, Solana or BNB Chain, from open DEX pair data cached sixty seconds, with risk flags (thin liquidity, pair under 24h old). The card may carry an 'Open in ' referral link, disclosed in its label; show it as is. Most new tokens go to zero. Read-only market data; not financial advice. [price: $0.01]

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": {
      "token": "<token>"
    },
    "name": "nft_price"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Optional chain: base, ethereum, polygon, avalanche, sei, solana or bsc.
`token`	Yes	The token: a contract or mint address (give chain too), or a symbol that resolves to one liquid pair.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the 60-second cache freshness, read-only nature, risk-flag behavior (thin liquidity, pair under 24h), and the embedded referral link. It omits error/not-found behavior and what happens when a symbol matches multiple pairs, so it falls short of fully transparent.

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?

The core capability is front-loaded, but the seven-field and seven-chain enumerations are verbose, and the trailing 'Most new tokens go to zero', 'not financial advice' and '[price: $0.01]' strings add noise without helping an agent decide or invoke.

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?

There is no output schema, so the description must describe return values — and it does, covering fields, risk flags and the referral link. Gaps remain around failure modes and pair selection when a symbol is ambiguous, but for a 2-parameter read tool this is largely complete.

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 both parameters are documented in the schema, so the baseline is 3. The description largely restates the schema's chain list and the address-vs-symbol rule rather than adding new semantics such as symbol resolution ambiguity handling.

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?

The description names the exact resource (token pair market data) and enumerates the returned fields (price, 24h change, liquidity, volume, market cap, pair age, pair link) plus the supported chains, so the agent knows precisely what it gets. It does not explicitly differentiate from siblings like nft_floor or nft_wallet, leaving that inference to the reader.

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?

There is no statement of when to choose this tool over nft_floor, nft_pumps or nft_wallet, and no exclusion conditions. The only usage-like instruction ('show it as is' for the referral link) concerns output presentation, not tool selection.

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

All DeskCrew - AI Chatbot, Helpdesk & Knowledge base tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?