Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NFT

Paid. AINFT (NFT) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/NFT.

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": "buy_tok_NFT"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it does disclose real behavioral traits: the call is paid, the exact cost and payment chains, that no account or API key is required, and that failed calls are not charged. What it omits is response shape (JSON vs text), data freshness/latency, and what counts as a 'failed' call for refund purposes.

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?

Sentences are short and front-loaded with the most decision-relevant fact ('Paid'), followed by returned fields, then cost, then access requirements. The telegraphic style ('Paid. AINFT (NFT) price: ...') is efficient, though the raw endpoint URL is arguably dead weight for an agent that only invokes the tool.

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 zero-parameter, single-endpoint data fetch with no output schema, the definition covers the essentials: what data comes back, what it costs, which chains pay, and that no credentials are needed. It is only slightly thin on return format and data recency, which matters because no output schema exists to fill that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which sets the baseline at 4; there is no parameter meaning left to explain because none exist. The description correctly implies the asset (NFT) is baked into the endpoint URL rather than being a caller-supplied argument.

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 a specific resource (AINFT/NFT) and enumerates exactly the fields returned: live USD price, 24h change and market-cap rank. That is a concrete verb-less but unambiguous data-retrieval purpose. It falls short of a 5 because it never names the obvious alternative (buy_crypto_price or the buy_tok_* family) to explain why an agent should pick this asset-specific tool.

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 when-to-use or when-not-to-use guidance and no mention of alternatives despite ~1000 sibling price tools. The only usage-adjacent content is cost/payment mechanics ('$0.01 USDC on Base or Solana'), which tells the agent the price of calling but not the condition under which 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