Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NAORIS

Paid. NaoX Protocol (NAORIS) 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/NAORIS.

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_NAORIS"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — a genuinely useful risk-reduction detail for a paid tool. Gaps remain around latency, rate limits, and freshness/caching of the quoted price.

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?

Five short fragments, zero filler: paid status first, then what you get, then cost/rails, then trust signals, then the endpoint. Every sentence adds information an agent needs before invoking a paid call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, paid, single-value lookup with no output schema, the description covers purpose, returned fields, cost, payment rails, and failure billing — everything needed to decide and invoke. The only omission is the raw response format, which is minor given the field list.

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, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly presents this as a parameterless single-asset lookup rather than implying optional filters that do not exist.

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?

States a specific resource (NaoX Protocol / NAORIS price) and enumerates the returned data: live USD price, 24h change, market-cap rank. The token identity is carried by the name and restated in prose, so an agent can tell it apart from the mass of buy_tok_* siblings by symbol. It does not, however, distinguish itself from generic price siblings such as buy_crypto_price or the parallel buy_coin_* family.

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

Usage Guidelines3/5

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

Implied usage is clear (fetch NAORIS price data), and the 'Paid. $0.01 USDC' framing signals this is a metered call to weigh against free alternatives. There is no explicit when-to-use / when-not-to-use guidance and no mention of the sibling tools an agent should compare against before spending money.

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