Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000033

Paid. Tradable APAC Diversified Finance Provider SSTN (PC0000033) 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/PC0000033.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden and does more than most: it discloses that the call is paid, the exact cost ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and critically that failed calls are not charged. Missing only edge behavior such as rate limits or latency expectations, which keeps it below 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.

Conciseness4/5

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

It is short and front-loads the fact that this is a paid call before the asset and payload details. The telegraphic style ('Paid. Tradable ... price: live USD price') is dense but readable, with every clause carrying information; nothing is filler.

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 tool this is close to complete: it covers the asset, the returned fields, cost, payment rails, auth requirements, failure charging, and the endpoint URL. Only return-format specifics (e.g. timestamp, numeric precision) are absent, which is a minor gap given the tool's simplicity.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description instead usefully specifies what the response contains (price, 24h change, market-cap rank), which is the relevant semantic detail for a no-arg tool.

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 verb+resource: it returns the live USD price, 24h change and market-cap rank for the single asset PC0000033 (APAC Diversified Finance Provider SSTN). The tool name encodes the ticker, so among the hundreds of buy_tok_* siblings the agent can tell which asset this covers. It does not, however, explicitly distinguish itself from nearby generic feeds like buy_crypto_price or buy_tok_PC.

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 it should call this when it needs the price of this particular asset. The description states preconditions for calling (no account, no API key), which is helpful, but never names an alternative tool or says when not to use this one, so routing among the price-related siblings is left to inference.

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