Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EXOD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and the shape of a success vs. failure response, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short fragments, front-loaded with what matters: 'Paid.' first, then the payload, then the cost and payment rails. Every sentence carries a distinct fact — cost, auth, billing policy, endpoint — with no padding. The only redundancy is the 'EXOD (EXOD)' ticker repetition.

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 0-param, no-output-schema tool, the description covers what the agent must know: the three returned fields, the payment requirement, and the billing behavior on failure. It is nearly complete; the remaining gap is a missing pointer to the closest sibling for cases where the caller wants a different asset or a free source.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless call by embedding the asset in the endpoint URL, so an agent knows no arguments are required.

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 (EXOD) and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. That is far more than a restatement of the name. However, it never distinguishes itself from the many similarly shaped siblings such as buy_coin_EXOD, buy_tok_* or buy_crypto_price, so an agent cannot tell from the description alone why this variant exists.

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: an agent infers 'call this when you need EXOD's spot price.' There is no explicit when-to-use statement, no exclusions, and no named alternative for the broad vs. per-coin price lookups in the sibling list. Adequate but leaves selection inference to the reader.

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