Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000101

Paid. Tradable NA Post-Settlement Legal Financing Receivables (PC0000101) 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/PC0000101.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 it does disclose meaningful behavior: it is paid, costs $0.05 USDC on Base or Solana, requires no auth, and failed calls are not charged. It does not explain the payment handshake (how the USDC is actually collected per call), rate limits, or whether the price is streamed or cached, which matters for an agent that must decide whether to pay.

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?

Six short clauses, front-loaded with 'Paid.' so cost is known before anything else, then payload, then payment logistics, then endpoint. Telegraphic style is appropriate for this format, though the fragments read as machine-generated and the URL could be separated more cleanly.

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 endpoint, the description covers the essentials an agent needs: what is returned, what it costs, which chains, that no credentials are needed, and the failure-billing policy. The main remaining gap is the mechanics of how the $0.05 payment is actually settled on invocation.

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 applies. The only variable is baked into the tool name and endpoint URL, which the description surfaces explicitly.

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 exact resource (PC0000101, 'NA Post-Settlement Legal Financing Receivables') and enumerates the payload: live USD price, 24h change, and market-cap rank. It is a fragment rather than a verb phrase, but an agent can still tell precisely what data it yields. It does not distinguish itself from the ~1000 sibling buy_tok_* tools beyond the embedded asset ID, which is the only real differentiator anyway.

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 implied rather than stated: fetch a price snapshot for this specific tokenized receivable. There is no explicit guidance on when to prefer this over generic siblings like buy_crypto_price or buy_tok_PC, and no exclusions. The 'No account, no API key' note removes setup friction but is not selection guidance.

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