Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CENT

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

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

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 a solid job: it discloses that calls are paid ($0.01 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and gives the endpoint URL. The main gap is that it never states rate limits, caching/freshness policy, or the failure/refund mechanics beyond 'not charged'.

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?

Extremely tight: a payment flag, the resource and its return fields, price and rails, auth/failure terms, and the URL, each in a fragment that earns its place. Cost and capability are front-loaded so an agent can decide quickly.

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, the description covers what is needed to call it: what it returns, that it costs money and how to pay, and that auth is unnecessary. It stops short of describing the response shape (JSON field names, units, timestamp), which is the only meaningful omission.

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 nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics are missing because none exist.

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 resource (Incentiv / CENT USD price) and enumerates exactly what is returned: live price, 24h change, market-cap rank. That is well beyond a tautology. It does not explicitly differentiate itself from the hundreds of sibling buy_tok_<SYMBOL> tools beyond the embedded ticker, so it falls short of 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?

Usage is implied rather than stated: an agent can infer this is the tool for CENT price data, and the cost/auth lines tell it what to expect. There is no explicit when-to-use / when-not-to-use guidance and no alternative named (e.g. buy_crypto_price or buy_coin_* equivalents), leaving routing to the agent.

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