Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MIM

Paid. MAGIC•INTERNET•MONEY (Bitcoin) (MIM) 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/MIM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged — non-obvious commercial behavior an agent must know before spending. It stops short of stating update frequency, latency, or rate limits.

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?

Front-loads 'Paid.' so the cost implication is the first thing read, then gives payload, price, prerequisites, and endpoint in a tight sequence. It is fragment-like rather than prose, but no sentence is padding.

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-param, no-output-schema price endpoint, the description covers the things an agent actually needs: what data comes back, what it costs, how to pay, failure billing, and the URL. The remaining gap is freshness/update cadence of the quoted price, which matters for a market-data tool.

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; baseline applies. The schema itself is empty and fully self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (MAGIC•INTERNET•MONEY / MIM) and the exact data returned: live USD price, 24h change, and market-cap rank. Against ~800 near-identical buy_tok_* siblings, expanding the ticker into a full name and listing the returned fields is what lets an agent confirm it picked the right token.

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 it should call this when it needs the MIM price. There is no explicit routing versus plausible alternatives such as buy_coin_MIM or buy_crypto_price, and no statement of when this paid endpoint is preferable to a free one.

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