Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FORM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 cost ($0.05 USDC), accepted chains (Base or Solana), that no auth/account is required, and that failed calls are not charged. It omits rate limits, latency, and how the payment is actually transacted (e.g., pre-authorized vs. per-call), which are the remaining behavioral unknowns for a paid tool.

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?

Five short fragments, each carrying distinct information: payment status, payload contents, price/rails, auth requirements, failure policy, endpoint. Nothing is repeated and the highest-value facts (that it costs money) are front-loaded.

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 tool with no output schema, the description covers what an agent needs: what comes back, what it costs, how to pay, and that failures are free. The one gap is that without an output schema it could spell out the response shape or units (e.g., rank as an integer) more explicitly.

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 description correctly implies no caller-supplied input is needed beyond the fixed endpoint.

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 exact resource (FORM token price) and enumerates the returned data: live USD price, 24h change and market-cap rank. Against hundreds of near-identical buy_tok_* siblings, the token name and payload contents are what distinguish it, which the description supplies. It stops short of a clean verb phrase, opening with the fragment 'Paid.' rather than something like 'Buy the FORM price feed'.

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 makes clear this is a paid endpoint and states the price, payment assets and that no account or API key is needed, which is real selection context. However, it never says when an agent should pick this over the adjacent buy_coin_* / buy_crypto_price style siblings, nor what happens if the caller lacks USDC on Base or Solana.

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