Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OPEN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does real work: it discloses cost, accepted payment rails, the absence of auth requirements, and the no-charge-on-failure policy. It omits freshness/latency and rate limits, which would matter for a live-price feed.

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?

Front-loads 'Paid.' and then gives purpose, price, terms, and URL in a tight sequence with no filler. The telegraphic, fragment-heavy style trades a little readability for density.

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?

With no parameters and no output schema, the description does the necessary work by naming the returned fields (price, 24h change, market-cap rank) and the payment contract. Only the response shape and data freshness 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 to disambiguate; the baseline applies. The description correctly implies the token symbol is baked into the endpoint rather than passed 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?

States a specific resource and verb-adjacent intent: 'OpenLedger (OPEN) price: live USD price, 24h change and market-cap rank,' which tells an agent exactly what data comes back. It does not explicitly distinguish itself from look-alike siblings such as buy_crypto_price or the buy_coin_* family, relying instead on the symbol 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 Guidelines3/5

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

Gives clear preconditions for a paid call ($0.05 USDC on Base or Solana, no account, no API key, failures not charged), which implicitly frames when to invoke it. There is no explicit when-to-use-versus-alternative guidance, e.g. why use this over buy_crypto_price or a buy_coin_* endpoint.

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