Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RSFIRO

Paid. rsFIRO (RSFIRO) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/RSFIRO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the paid model, the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What is missing is how payment is actually settled (e.g., payment header/x402 flow) and any rate-limit or freshness caveats.

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?

Telegraphic and front-loaded: payment flag first, then what data is returned, then cost/rails, then failure policy, then endpoint. Every clause conveys actionable information and there is no 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 paid lookup with no output schema and no annotations, the description covers cost, payment rails, auth requirements, failure billing, returned fields, and the literal endpoint. Only the settlement mechanism and response shape (JSON keys, caching/freshness) remain unspecified.

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 the baseline is 4 and there is nothing further the description could add. The token identity is baked into the endpoint, which the description makes explicit.

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 the exact resource (rsFIRO/RSFIRO) and the exact payload returned (live USD price, 24h change, market-cap rank), which is more than the name alone conveys. It does not explicitly contrast with siblings like buy_crypto_price or the other buy_tok_* entries, so differentiation relies on the token 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative (e.g., buy_crypto_price for a general quote vs. this single-token endpoint). The only contextual cue is 'Paid' plus a price, which tells the agent a cost is incurred but not when to prefer this tool.

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