Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000077

Paid. Tradable Singapore Fintech SSL (PC0000077) 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/PC0000077.

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

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 burden and does reasonably well: it declares the tool is paid ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Missing are rate limits, latency, and response freshness guarantees, but the core behavioral contract is disclosed.

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?

Dense and front-loaded: what it is, what it returns, what it costs, how to pay, and the raw endpoint, all in a few short sentences with no filler. The telegraphic fragment style is slightly clipped but nothing is wasted and the key constraint (Paid) leads.

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 zero-parameter, no-output-schema tool, the description covers everything an agent needs: asset identity, exact returned fields, price and payment method, auth requirements, failure billing, and a direct URL. There is no meaningful gap left for the agent to guess at.

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 no parameter semantics to convey. The baseline of 4 applies; the description correctly does not invent parameters and instead spends its words on asset identity and payment terms.

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 (Singapore Fintech SSL, ID PC0000077) and the specific payload: live USD price, 24h change, and market-cap rank. This is far clearer than the opaque tool name alone. It does not explicitly contrast itself with the hundreds of sibling buy_tok_* / buy_crypto_price variants, but the specific asset identifier does the differentiation implicitly.

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?

Payment rails, cost, and the no-account/no-API-key constraint are stated, which gives context for invoking it. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to an alternative such as buy_crypto_price or the generic buy_tok_PC entry, leaving the agent to infer that this is the single-asset variant.

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