Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CHFSAFO

Paid. Spiko Amundi Overnight Swap Fund (CHF) (CHFSAFO) 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/CHFSAFO.

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

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 supplied, the description carries the full behavioral burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and crucially that failed calls are not charged. It does not state data freshness beyond 'live', rate limits, or the response shape.

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?

A single tight paragraph with the cost and payment terms front-loaded ('Paid.'), followed by the data returned and the access/pricing conditions. Slightly compressed phrasing ('price: live USD price') and an inline URL are minor inefficiencies but nothing is wasted.

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-annotations, no-output-schema endpoint, the description covers what is returned (price, 24h change, rank), cost, payment rails, authentication requirements, and failure charging. Missing only response structure and update cadence, which are small gaps given the tool's simplicity.

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 to disambiguate; baseline is 4. The description correctly implies the token is fixed by the tool identity rather than passed as an argument, which prevents an agent from searching for a symbol parameter.

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?

Names a specific resource (Spiko Amundi Overnight Swap Fund, ticker CHFSAFO) and a specific output (live USD price, 24h change, market-cap rank). The verb 'buy' in the name plus 'Paid' in the description makes the commercial nature explicit. It does not explicitly contrast with sibling tools such as buy_crypto_price or the other buy_tok_* variants, relying on the symbol in the name for differentiation.

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 implied rather than stated: an agent can infer this is the tool for CHFSAFO price data and that payment is required. There is no explicit when-not-to-use guidance, no mention of when to prefer buy_crypto_price or a bundle, and no prerequisites beyond the payment note.

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