Skip to main content
Glama

SouthPow crypto & market data

buy_tok_REBOOT

Paid. Reboot (REBOOT) 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/REBOOT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it delivers meaningful context: paid call at $0.05 USDC on Base or Solana, no account or API key required, and failed calls are not charged. It does not cover rate limits, latency, or output format beyond the field list, keeping it short of a 5.

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?

One dense block that front-loads the 'Paid' flag before the payload description, then pricing, then access terms, then endpoint. Every sentence carries useful information; the raw URL at the end is slightly extraneous for an agent that invokes via MCP rather than HTTP.

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 paid price lookup with no output schema and no annotations, the description supplies the fields returned, the cost, the payment chains, and the failure-charging policy. Only the absence of any sibling routing and exact response shape leaves a small gap.

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 no parameter meaning to convey; the schema is empty and the description correctly avoids inventing inputs. Baseline 4 applies for a zero-parameter tool.

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 verb+resource (live USD price for REBOOT) and enumerates the exact return fields: 24h change and market-cap rank. It is unambiguous about what the tool returns, though it never differentiates itself from the adjacent buy_crypto_price sibling, which appears to offer similar data.

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 implied by the token-specific naming and the payload description, but there is no explicit statement of when to pick this over buy_crypto_price or any other pricing sibling. Cost and payment rails are stated, which helps the agent decide, but no when-not-to-use guidance is given.

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