Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000097

Paid. Tradable LatAm Fintech SSTN (PC0000097) 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/PC0000097.

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

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?

No annotations exist, so the description carries the burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It does not cover rate limits, caching/freshness of the 'live' price, or what an error response looks like, which keeps it below 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?

Tight and front-loaded: 'Paid.' first, then the resource and returned fields, then cost/chain/access terms. Every sentence carries information. The raw endpoint URL is arguably redundant for an agent but is short and harmless.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless price lookup with no output schema, the description supplies what the agent otherwise could not know: the returned fields, the payment rail and amount, and the no-account/no-charge-on-failure terms. There is no structured field left unexplained for a tool this simple.

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-parameter tool, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is empty and fully covered; nothing in the description misdescribes an input.

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 a specific resource (PC0000097, a LatAm Fintech SSTN) and the exact payload: live USD price, 24h change, market-cap rank. The token id is embedded in both name and description, which separates it from the many sibling buy_tok_* tools, though the description never explicitly frames itself as the PC0000097 variant of a family.

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 can infer it is called when a price for this instrument is needed, and it is told the cost and chains. There is no explicit when-not-to-use guidance or pointer to the nearby siblings (e.g., buy_crypto_price, other buy_tok_PC* tools) that would route the agent correctly.

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