Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EURI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 disclosure burden and does a solid job: it states the call is paid, the exact cost ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only rate limits, retry/timeout behavior, or what constitutes a 'failed' call.

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?

Six short fragments, front-loaded with the 'Paid.' flag, then purpose, then price/payment terms, then honest failure policy, then endpoint. Dense and waste-free; the trailing raw URL is mildly redundant given the tool name but serves as documentation.

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-input, zero-output-schema purchase tool, the description covers what is bought, what the payload contains, what it costs, how to pay, and failure billing. Only the exact response shape (field names, currency formatting) and freshness/staleness of the price are left unstated.

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 in the schema for the description to clarify; baseline for a 0-param tool is 4. The description correctly implies the asset is fixed by the endpoint, so no input semantics are needed.

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 asset (Eurite/EURI) and enumerates exactly what data is returned: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from non-price siblings such as buy_fx_eur or buy_tvl_*, but it never explains how it differs from the many near-identical siblings like buy_coin_EURI or buy_crypto_price, leaving that inference to the ticker in the name.

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?

There is no when-to-use or when-not-to-use guidance at all. In a catalog containing buy_crypto_price, buy_coin_EURI, and hundreds of buy_tok_* tools, the agent gets no signal about which one to select for a given query. Payment logistics are covered, but selection guidance is entirely absent.

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