Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ERG

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the payment model, price, supported chains, and that failed calls are free — meaningful behavioral context rarely found in annotations. It stops short of stating rate limits, latency, caching/freshness of the 'live' price, or whether repeated calls are billed each time.

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?

Four short sentences, front-loaded with the payment flag and the payoff (what data you get), followed by cost, access requirements, billing guarantee, and endpoint. No filler; each clause adds decision-relevant information.

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-param tool with no output schema, the description covers purpose, return fields, cost, and access constraints — enough to call it correctly. Minor gaps are freshness guarantees and response format, though the endpoint URL lets an agent inspect the contract if needed.

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 clarify beyond the schema; baseline 4 applies. The description correctly implies a parameterless call by hardcoding the asset and endpoint.

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 resource (Ergo/ERG) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. Against hundreds of near-identical buy_tok_* siblings this is the differentiating information an agent needs. It lacks an explicit verb ('get'/'fetch'), but the intent is unambiguous.

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?

It supplies useful preconditions for calling (no account, no API key, $0.05 USDC on Base or Solana, failures not charged), which tells the agent it can invoke freely. It never routes the agent between this and adjacent alternatives like buy_crypto_price or buy_coin_* tokens, so the choice among siblings is left to inference from the ticker name.

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