Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NAT

Paid. DMT-NAT (NAT) 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/NAT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the $0.01 USDC charge, accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not billed. Missing are rate limits, latency, and whether the payment is per call or pre-funded, which keeps it short of a 5.

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?

Telegraphic but front-loaded: payload, then price/payment terms, then endpoint. Every clause carries a distinct fact. The fragment style ('Paid.') is slightly terse for an agent parsing it, but no sentence is wasted.

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 no-parameter, no-output-schema purchase tool, the description covers what comes back (price, 24h change, cap rank), what it costs, and how to pay. Return shape details and freshness guarantees would push it to 5, but an agent has enough to call and budget correctly.

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?

Zero parameters, so the baseline is 4; there is nothing schema-side that needs compensating for. The endpoint URL is included, which is informational rather than parameter semantics.

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 the specific resource and payload: DMT-NAT price, live USD price, 24h change and market-cap rank. That is far more than the bare name, but it never contrasts itself with adjacent siblings such as buy_crypto_price or buy_coin_* feeds, so the agent must infer that this is the NAT-specific variant.

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?

Usage is only implied by the token symbol and the enumerated return fields; there is no explicit statement of when to pick this over buy_crypto_price or another price tool. The 'Paid' prefix hints at cost tradeoffs but gives no alternative routing.

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