Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FIRO

Paid. Firo (FIRO) 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/FIRO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 load, and it does disclose the important commercial facts: it is a paid call at $0.05 USDC on Base or Solana, needs no account or API key, and failed calls are not charged. It says nothing about data freshness or latency, rate limits, response format, or whether a retry after failure is safe, which are the remaining behavioral gaps for a paid endpoint.

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 short, front-loaded with the paid flag and the resource, and every clause adds something concrete: payload fields, price, payment chains, auth, billing on failure, and the endpoint URL. The staccato phrasing is efficient rather than padded, although the bare URL adds little for an agent that invokes the tool rather than the endpoint.

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 annotations and no output schema, the description correctly compensates by enumerating the returned fields (price, 24h change, market-cap rank) and the commercial constraints. It is nearly complete for a single-argument-free read, missing only freshness or latency expectations and the response format.

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 and the schema is empty, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description does not waste effort inventing parameter meaning, which is correct here.

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 (Firo/FIRO price) and the payload it returns: live USD price, 24h change, market-cap rank. That is enough to tell it apart from the hundreds of sibling buy_tok_<SYMBOL> endpoints, though it does not distinguish itself from other price tools such as buy_crypto_price or the buy_coin_* family.

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?

Usage is only implied: the agent infers it should call this when it wants FIRO pricing data. The description gives no when-to-use rule, no exclusion, and never names an alternative for the same token or for broader price queries, which matters given the very dense sibling set.

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