Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HUNDRED

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

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

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 at all, the description carries the full burden and does a better-than-average job: it discloses that the call is paid ($0.05 USDC), names both accepted payment rails (Base or Solana), states no account or API key is required, and guarantees failed calls are not charged. Remaining gaps are rate limits, response freshness/caching, and the shape of the returned data.

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?

Roughly three short sentences plus a URL, with no wasted prose. The opening fragment 'Paid.' and the redundant 'HUNDRED (HUNDRED)' are slightly telegraphic, but the price/rail/access information is all load-bearing and delivered up front.

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, no-output-schema price lookup, the definition supplies what an agent actually needs: what data comes back, what it costs, how to pay, and that no credentials are needed. A brief note on response format (JSON field names) and update frequency would close the last gap.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the token identity is correctly baked into the endpoint rather than exposed as an argument.

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 specific resource (HUNDRED token) and the exact payload returned: live USD price, 24h change, and market-cap rank. That is far more informative than the opaque tool name, though it does not explicitly contrast itself with the generic sibling buy_crypto_price or the buy_coin_* family, so an agent must infer the distinction from the ticker alone.

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 statement of when to choose this over buy_crypto_price, buy_coin_*, or the buy_yields_* price tools. The only guidance offered is access-oriented ('No account, no API key'), which tells the agent how the call is authorized but not when the call is appropriate or what the alternatives are.

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