Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CHFAU

Paid. AllUnity CHF (CHFAU) 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/CHFAU.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and mostly delivers: it states the tool is paid, the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — the key financial risk for an agent. It omits rate limits, latency, and whether the price is real-time or last-cached, 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?

Six short segments, front-loaded with the paid flag and the returned fields before the cost and logistics. The trailing literal URL is marginal value for an agent that already has the endpoint, but nothing is padded or repetitive.

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, output-schema-less paid data endpoint, the description covers what is returned, what it costs, how to pay, and what happens on failure. The remaining gap — response shape and price freshness — is small relative to this tool's complexity.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly conveys that the token is fixed by the tool itself 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?

The description names the specific resource (AllUnity CHF / CHFAU) and enumerates exactly what it returns: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the many buy_coin_* / buy_tok_* siblings, though the verb is only implied by the colon construction rather than stated as 'fetches' or 'returns'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this tool versus alternatives such as buy_crypto_price or any of the buy_coin_CHF-adjacent siblings, and no guidance on call frequency or caching. The token name implies the use case, but the description never routes the agent to or away from a 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