Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EURC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 well: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), the absence of auth requirements, and the failure policy (failed calls not charged). It omits anything about response format, latency, or freshness of the 'live' price, which keeps it short of 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?

Front-loaded with 'Paid.' followed by the payload, cost, access terms, and URL — each clause earns its place and there is no filler. Minor redundancy in 'EURC (EURC)' and the raw URL sitting inline with no framing.

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 endpoint with no output schema, the description covers the three things an agent needs: what data it returns, what it costs, and how payment/access works. A brief note on whether the price is a snapshot vs streaming, or expected response shape, is the only gap.

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 schema semantics to add and the baseline applies. The description does not waste words inventing parameters, and the embedded URL implicitly documents the fixed endpoint shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb/resource pair implicitly (fetch EURC price) and enumerates exactly what comes back: live USD price, 24h change, and market-cap rank. The token symbol is pinned in both name and description, so it is unambiguous against the many sibling token tools (buy_tok_EURE, buy_tok_EURCV, buy_coins_*).

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 description tells the agent the call is paid and requires no account or API key, which is useful selection context, but it never says when to prefer this over alternatives such as buy_crypto_price or buy_coin_* siblings, nor when not to call it. Usage is implied by the data fields offered rather than stated.

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