Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN64

Paid. Chutes (SN64) 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/SN64.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 the cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining how payment is actually settled or whether the charge is per-call or per-response, which is the one remaining behavioral unknown for a paid tool.

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?

It is a tight, front-loaded block: payment status first, then the payload, then cost, auth, billing policy, and endpoint. The telegraphic fragment style ("Paid.") is efficient but slightly clipped, and the raw URL is arguably metadata rather than guidance.

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 purchase tool with no output schema, the description covers everything an agent needs to decide and call: what data comes back, what it costs, where payment lands, and the no-charge-on-failure guarantee. Only the response shape and latency are unstated, which is minor at this complexity.

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; the baseline of 4 applies. The description implicitly confirms the asset is baked into the endpoint, so the agent knows no symbol argument is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (Chutes / SN64 token price) and the payload it returns: live USD price, 24h change, market-cap rank. An agent can distinguish it from buy_crypto_price or the other buy_tok_SN* siblings without opening a schema, since the subnet is named explicitly.

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 word "Paid" and the price-data subject; there is no statement of when to prefer this over buy_crypto_price or a sibling subnet tool, and no conditions under which it should be skipped. Adequate but leaves routing to inference.

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