Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BOX

Paid. DeBox (BOX) 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/BOX.

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

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 no annotations, the description carries the whole burden and does well: it discloses that the call is paid, the exact price and accepted payment rails, that no auth is required, that failed calls are not billed, and the endpoint URL. It omits freshness/caching behavior, rate limits, and error-response shape, which keeps 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?

Dense and front-loaded: 'Paid.' immediately signals the commercial constraint, then the payload, then cost/auth terms. The trailing raw URL is slightly extraneous for agent decision-making but costs little.

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, no-output-schema lookup, the description covers the return fields, the cost, payment options, and the absence of auth — everything needed to invoke it. Only secondary operational details (latency, rate limits, error behavior) are missing.

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 no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the token is fixed by the tool identity rather than passed as an argument.

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 a specific resource and its payload precisely: 'DeBox (BOX) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. It does not explicitly contrast itself with near-neighbors like buy_crypto_price or the buy_tok_* family, relying on the token symbol alone to differentiate.

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?

It supplies commercial context (paid, $0.05 USDC on Base or Solana, no account or API key, failed calls not charged) which helps an agent judge whether to invoke, but there is no explicit when-to-use/when-not guidance and no named alternative such as the generic crypto price sibling.

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