Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GEODE

Paid. Geode Chain (GEODE) 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/GEODE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 does well on the commercial/auth side: it states the $0.05 USDC cost, the two accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It says nothing about rate limits, latency, caching/staleness of the price, or what a failure looks like, so material behavior for a paid call remains undisclosed.

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?

It is a dense, front-loaded fragment set: what the data is, what it costs, how to pay, and the raw URL, with no filler sentences. The telegraphic style ('Paid.' / 'URL ...') is slightly abrupt but each element earns its place.

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, no-output-schema tool, the description covers the returned fields, the payment mechanics, and the exact endpoint, which is nearly everything an agent needs. The remaining gap is failure/retry semantics and freshness of the quoted price, which matter for a paid call but are secondary.

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 and the baseline of 4 applies. The description correctly implies the token is baked into the endpoint rather than supplied as an argument.

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 and scope: 'Geode Chain (GEODE) price: live USD price, 24h change and market-cap rank', so an agent knows exactly what data comes back. It does not differentiate itself from near-siblings such as buy_crypto_price or the easily confused buy_coin_GEOD, leaving the agent to infer that this is the paid per-token quote endpoint.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for cheaper or bulk price lookups. The only routing signal is implicit: 'Paid' plus the $0.05 price tells an agent this costs money, which is a hint but not a stated selection rule.

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