Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0016245

Paid. NA Capital-as-a-Service SSTN (PC0016245) 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/PC0016245.

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

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?

With no annotations, the description carries the full burden and mostly delivers: it discloses that the call is paid, the exact cost ($0.05 USDC), both accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Those are exactly the operational facts an agent needs before spending money. It omits rate limits, latency, and payment mechanics, keeping 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?

The whole definition is a handful of short clauses that front-load the most decision-relevant facts (paid, what data, how much, which chains). The URL at the end is slightly redundant with the token code but is cheap and useful. No filler sentences.

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 paid price lookup, the definition covers cost, payment chains, auth requirements, failure billing, and even enumerates the returned fields (price, 24h change, market-cap rank), which compensates for the missing output schema. Only latency and rate-limit detail are absent, which is minor at this complexity.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies a parameterless call, with the token identity baked into the tool itself rather than passed 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 a concrete verb-plus-resource: it returns the live USD price, 24h change, and market-cap rank for one specific instrument, PC0016245 (NA Capital-as-a-Service SSTN). That is far more specific than the bare name and separates it from the hundreds of buy_tok_* siblings by identifying the exact token. It stops short of an explicit 'not for other tokens' statement, which is why it is not a 5.

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?

Use is implied by the 'price' framing and the identifying token code, so an agent can infer this is the call for PC0016245 data. However, there is no explicit when-to-use or when-not guidance, no statement about how it relates to buy_crypto_price or the other buy_tok_* tools, and no note on refresh cadence. Adequate but leaves routing 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