Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GALA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the cost, accepted payment chains, that no credentials are needed, the failure-charge policy, and the underlying endpoint URL. It stops short of rate limits, latency, or how payment is actually authorized per call, which leaves some operational uncertainty for an agent looping over many tokens.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense line: it leads with 'Paid.', then the data returned, then cost and rails, then guarantees and endpoint. Every fragment carries information and nothing is padded.

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 lookup with no output schema, the description covers what an agent needs: the fields returned, the price, payment options, and the failure policy. It could be marginally more complete by clarifying its relationship to the free-looking buy_coin_GALA sibling.

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 applies. The description correctly implies the ticker is fixed by the tool itself rather than passed in, which is the one semantic point that matters.

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 the exact payload (live USD price, 24h change, market-cap rank) for a named ticker, so an agent knows precisely what data comes back. Sibling differentiation is carried largely by the tool name and the ticker rather than by the prose, so it falls just short of a 5.

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?

Gives the commercial context (paid, $0.01 USDC on Base or Solana, no account or API key, failed calls not charged), which is real guidance for deciding whether to call it. It never says when to prefer this over the obvious alternatives, notably the sibling buy_coin_GALA and buy_crypto_price, which is the main ambiguity an agent faces here.

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