Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EURCV

Paid. EUR CoinVertible (EURCV) 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/EURCV.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well: it discloses the paid cost, payment currency and chains, no-account/no-API-key access, no charge for failed calls, and the endpoint URL. It still omits rate limits and the exact payment mechanics, but the key behavioral constraints are present.

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 description is compact and front-loads the paid status and core purpose, then follows with pricing, access constraints, and the URL. The fragment style is efficient, though the payment details and endpoint URL could be separated more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-argument price lookup, the description covers the return fields, cost, authentication model, failure billing, and endpoint. However, given the enormous sibling set of similar price tools, it lacks the routing context needed to confidently select this tool over near alternatives.

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 for the description to add beyond the empty schema. This is the baseline expectation for a no-parameter tool.

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 specific asset (EURCV) and the exact data returned: live USD price, 24h change, and market-cap rank. It is clear what the tool does, though it does not explain how it differs from sibling families such as buy_crypto_price or the buy_coin_* token tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states that the call is paid and lists the cost, but gives no explicit guidance on when to use this tool versus alternatives. With hundreds of sibling price tools, the lack of routing guidance between buy_tok_*, buy_coin_*, buy_stable_*, and buy_crypto_price is a meaningful gap.

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