Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000031

Paid. Tradable NA Rent Financing Platform SSTN (PC0000031) 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/PC0000031.

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

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 supplied, the description carries the full burden and does a solid job: it discloses that the call is paid ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — exactly the risk facts an agent needs before spending. It omits rate limits, expected latency, and the response shape, 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?

The paying condition ('Paid.') is front-loaded, followed by asset identity, returned fields, cost/rails, and the endpoint URL — a logical order with no filler sentences. The raw URL and repeated identifier cost a little density, but every element is functional.

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 no-parameter paid price endpoint with no output schema, the definition covers what the agent must know: asset identity, the three returned fields, price, payment rails, and failure billing. Only the precise response format and any freshness/rate-limit guarantees are missing, which are minor for a zero-argument read.

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 document and the baseline of 4 applies. The description correctly avoids inventing any parameter discussion.

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 asset covered ('Tradable NA Rent Financing Platform SSTN (PC0000031)') and the exact data returned ('live USD price, 24h change and market-cap rank'), which lets an agent tie the opaque tool name to a real subject without opening the schema. It does not explicitly differentiate itself from the many sibling buy_tok_* tools, but the embedded identifier makes the scoping self-evident.

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 by the identifier and the 'price' URL, so an agent can infer this is the price lookup for PC0000031. There is no explicit statement of when to prefer this over a general price tool (e.g. buy_crypto_price) or when not to call it, leaving 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