Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NYM

Paid. Nym (NYM) 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/NYM.

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

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?

With no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is needed, and that failed calls are not charged. It stops short of describing response format, latency, or rate limits.

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?

Front-loaded with 'Paid.' then the payload, then payment terms, then auth behavior, then URL — every sentence adds information. Formatting is telegraphic but readable; the bare URL could arguably be framed as an endpoint rather than sitting as a trailing fragment.

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 paid lookup with no output schema, the description covers cost, chain, auth, failure billing, and which metrics come back — enough to call it correctly and predict charges. Missing only the response shape and freshness/latency characteristics, which matter slightly for a price feed.

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 to disambiguate; the schema drives the entire call shape. Baseline 4 applies, and the description correctly says nothing misleading about inputs.

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 resource precisely (NYM/USD price) and enumerates the returned values: live USD price, 24h change, market-cap rank. It doesn't spell out the verb (the 'buy_' prefix plus 'Paid' implies a purchase-per-call), and it doesn't explicitly contrast itself with the many sibling buy_tok_* / buy_coin_* endpoints, but the coin-specific scope makes it unambiguous.

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 explicit statement of when to use this tool versus alternatives such as buy_coin_NYM or buy_crypto_price, and no exclusions. The payment and auth constraints ('$0.01 USDC on Base or Solana', 'No account, no API key') imply eligibility conditions but are not framed as usage guidance.

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