Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USTC

Paid. TerraClassicUSD (USTC) 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/USTC.

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

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 well: it discloses the paid/billing model, the exact price and accepted chains, the absence of auth requirements, and the failure-charge policy. It also implies the returned fields. It omits response encoding, data freshness/refresh cadence, and any rate limit, which keeps it from 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.

Conciseness5/5

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

Five short fragments, front-loaded with 'Paid.' so the cost signal precedes everything, then the payload, price, auth, billing policy, and URL. No sentence is redundant and nothing is buried.

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-annotation, no-output-schema tool, the description covers what it returns, what it costs, where to pay, and what happens on failure. Missing only freshness and response-format details, which are minor for a single fixed-resource price lookup.

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 properties, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool is 4, and the description correctly implies no inputs are needed beyond the payment.

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?

Names the specific asset (TerraClassicUSD/USTC) and the exact payload: live USD price, 24h change, market-cap rank. An agent can tell this apart from the generic buy_crypto_price and from the hundreds of buy_tok_* / buy_coin_* siblings because the resource is spelled out in both ticker and full name. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than 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?

Provides practical preconditions: it is a paid call, costs $0.01 USDC on Base or Solana, needs no account or API key, and failures are not billed. That is real usage context. However, it never states when to prefer this over alternatives (e.g. a generic price tool or a cached quote) or when not to call it, leaving selection 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