Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TDCCP

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

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

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 provided, so the description must carry the behavioral load, and it does: it discloses the cost, accepted payment chains, that no auth is required, and that failed calls are not charged. Freshness/latency and rate limits are the remaining gaps, but the billing and access semantics are unusually well covered.

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?

Front-loaded with 'Paid.' and the returned fields, then cost, then access terms, then endpoint — a sensible order with no filler sentences. Minor waste in repeating the ticker as 'TDCCP (TDCCP)' and in spelling out the raw URL.

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?

With no parameters and no output schema, the description supplies what an agent needs: what data comes back, what it costs, how to pay, and that failures are free. Only return formatting (units, rounding) is left implicit.

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 meaning to convey; the baseline is high. The description correctly implies nothing needs to be supplied since the token is fixed in the tool name and URL.

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?

States the specific resource (TDCCP token) and the exact payload returned: live USD price, 24h change, and market-cap rank. That distinguishes it from generic siblings like buy_crypto_price, though it never names those alternatives explicitly.

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?

The '$0.01 USDC on Base or Solana' and 'No account, no API key' lines establish the purchase preconditions, which is useful. However, there is no guidance on when to pick this per-token tool over buy_coin_TDCCP, buy_crypto_price, or buy_tok_* peers.

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