Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EXC

Paid. ElonXCat (EXC) 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/EXC.

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

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 provided, the description carries the full burden and does a solid job: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. What it does not cover is response shape/timing beyond the field list, or what happens on rate limits or partial failures.

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-loaded with 'Paid.' and then the resource and result fields; every sentence carries information (price, payment, auth, failure policy, endpoint). The telegraphic, fragment-heavy style is efficient but slightly reads like a listing rather than prose.

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 purchase tool, the description supplies the payment amount, chains, auth posture, and the three values returned, which is enough to call it correctly and predict the cost. Only minor gaps remain around response format and any rate limits.

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 and the baseline of 4 applies. The description correctly adds no fake parameter guidance and instead spends its words on cost and output content.

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?

Names the exact asset (ElonXCat / EXC) and enumerates the data returned: live USD price, 24h change, and market-cap rank. An agent can immediately tell what it gets and how it differs from generic siblings like buy_crypto_price or the buy_coin_* family.

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?

The leading 'Paid.' plus the $0.05 USDC price gives an implicit selection rule (paid, single-token quote), but the description never explicitly contrasts this with buy_crypto_price, buy_coin_EXC-style siblings, or a free alternative. The when-to-use context is inferable, not stated.

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