Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ACE

Paid. Fusionist (ACE) 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/ACE.

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

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 full burden and does well: it discloses cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged, plus the endpoint URL. It stops short of freshness/latency and of how the payment is actually settled (e.g. 402 handshake), which matters for an agent that must pay.

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?

Terse and front-loaded: paid status, then what data is returned, then cost and prerequisites, then endpoint. The telegrammatic fragments ('Paid.', bare URL) are efficient rather than wasteful, though the URL could be folded into a shorter clause.

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 paid lookup with no output schema, the description supplies output fields, price, payment chains, auth requirements, failure-charge policy and endpoint, which is nearly everything an agent needs. The missing piece is the mechanics of paying and whether the price is real-time or cached.

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?

Zero input parameters, so the schema offers nothing to interpret and there is no parameter meaning to add. Baseline 4 applies; nothing in the description contradicts or clutters this.

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 data payload: 'Fusionist (ACE) price: live USD price, 24h change and market-cap rank.' The token symbol in the name plus the description clearly separates it from the hundreds of buy_tok_* siblings, though it never acknowledges the generic buy_crypto_price tool that could also serve this request.

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 by the token-specific name; there is no explicit statement of when to pick this over buy_crypto_price or over a sibling token tool, and no exclusions. The surrounding sentences cover payment terms and auth ('No account, no API key'), not selection guidance.

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