Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LON

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

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

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?

With no annotations, the description carries the full burden and does well: it discloses the paid model, the accepted payment chains, the absence of authentication, and the failure-billing policy — all behavior an agent cannot infer from structured fields. It stops short of stating rate limits or whether the price is real-time versus delayed beyond the word 'live'.

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-loaded with 'Paid' and the payload description, then the cost and access terms, then the endpoint URL. The telegraphic phrasing is dense but every clause (cost, chains, auth, billing, URL) carries information; nothing is filler.

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 parameterless price lookup with no output schema, the description covers what is returned (USD price, 24h change, market-cap rank), what it costs, and how to reach it. It could add the response shape or freshness guarantee, but nothing essential for correct invocation is missing.

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 input schema has zero parameters, so the baseline is 4. The description usefully reinforces that no account or API key is needed, confirming the call is genuinely parameterless with no hidden auth input.

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 (Tokenlon/LON) and the exact data returned: live USD price, 24h change, and market-cap rank. That is enough to identify the tool among the hundreds of ticker-scoped siblings without opening the schema, though it never explicitly contrasts itself with generic alternatives like buy_crypto_price.

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 states the commercial context ($0.05 USDC on Base or Solana, no account, no API key) and that failed calls are not charged, which helps an agent decide whether to pay. But it gives no explicit when-to-use guidance, no mention of when a generic price tool would be preferable, and no note on caching or freshness for repeated calls.

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