Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GEKKO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 well: it discloses that the call is paid, the exact price and accepted settlement chains, that no account or API key is needed, and that failed calls are not charged. What is missing is failure semantics beyond billing (e.g., what an error looks like, latency, or response envelope), though the returned fields are named.

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?

Every clause earns its place: data returned, price, payment rails, auth requirement, billing on failure, endpoint. The cost signal is front-loaded with 'Paid.' and there is no filler whatsoever.

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

Completeness5/5

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

For a zero-argument, fixed-asset price lookup with no output schema, the description covers what matters: the fields returned, the price and payment method, the chains, and the no-charge-on-failure policy. An agent has everything needed to decide and call correctly.

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; the baseline of 4 applies. The URL is included, which is incidental rather than parameter-related.

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?

States a specific resource and the exact data returned: 'GEKKO (GEKKO) price: live USD price, 24h change and market-cap rank.' That is far more informative than the bare tool name. It does not, however, distinguish itself from the near-identical sibling patterns buy_coin_GEKKO and buy_crypto_price, so an agent cannot tell from the description alone which of those to pick.

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 only implied: you would call it when you need the current GEKKO quote. The payment terms ('$0.05 USDC on Base or Solana') do give a real cost gate that helps an agent decide whether to spend, which is more than nothing. But there is no explicit when-not guidance and no routing to the cheaper or alternative siblings.

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