Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WOULD

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

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

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 zero annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment chains, that no account or API key is required, and that failed calls are not charged. It omits response format, latency, and caching/freshness semantics 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?

Roughly four short sentences with cost and payload front-loaded and no filler. The telegraphic 'Paid. would (WOULD) price:' phrasing is slightly clipped and the raw URL at the end reads as metadata rather than instruction, but nothing is wasted.

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, output-schema-less data purchase, the description covers what is returned (price, 24h change, rank), what it costs, how to pay, and that failures are free — enough for an agent to call it correctly. Remaining gaps, such as response shape and freshness guarantees, are minor at this complexity.

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 no parameters, so the baseline is 4 and there is nothing the description could add. The embedded URL confirms the token is baked into the path rather than supplied by the caller, which is consistent with the empty schema.

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 payload: 'would (WOULD) price: live USD price, 24h change and market-cap rank.' The token is named, which is what separates it from the hundreds of buy_tok_* siblings. It does not, however, differentiate itself from likely alternatives such as buy_crypto_price or buy_coin_* style endpoints.

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?

The description gives useful decision context in the form of pricing ('$0.05 USDC on Base or Solana'), no-account access, and 'Failed calls not charged', which lets an agent judge cost and risk. It never explicitly says when to choose this endpoint over another price source, nor whether it is a one-shot snapshot versus time series.

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