Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MIRA

Paid. Mira (MIRA) 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/MIRA.

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

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 does real work: it declares the tool is paid ($0.05 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — all non-obvious behavioral facts, plus the endpoint URL. However, no output schema exists, so the return shape is only sketched (price, 24h change, rank) with no field names, format, or staleness/freshness guarantees.

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 and front-loaded: 'Paid.' appears first so the agent sees the cost before the payload description. The single URL and the split payment rails are compact; 'No account, no API key' is mildly redundant but still earns its place as a friction signal.

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 single-asset price tool with no output schema, the description covers cost, payment chains, auth requirements, billing on failure, and the three data points returned. Only freshness/caching behavior and the literal response shape are left unstated, which is a minor gap 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 there is nothing for the description to disambiguate; the input schema is empty and fully described. Baseline 4 applies.

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 a specific resource (Mira/MIRA) and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. An agent can tell this is a single-token price lookup, but nothing distinguishes it from the generic buy_crypto_price sibling, which is never mentioned.

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: an agent infers 'call this to get MIRA's price'. The description states prerequisites (no account, no API key) and payment mechanics, but gives no when-to-use condition and no guidance on when to prefer buy_crypto_price or another token tool instead.

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