Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FLIP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does well on the parts that matter for a paid endpoint: cost ($0.01 USDC), accepted payment chains (Base or Solana), no account or API key required, and no charge on failure. What it omits is price freshness/update cadence, any rate limit, and how the payment handshake is actually performed, so an agent knows the economics but not the mechanics.

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?

Six short fragments, front-loaded with the most decision-relevant token ('Paid') followed immediately by the resource and return payload. Nothing is padded; the pricing, auth, and failure-charge facts each occupy a single 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-parameter, no-output-schema endpoint the description does the right work by listing the three returned fields and the endpoint URL. It stops short of stating units/precision for the 24h change (percent vs. absolute) or the currency basis of the price, which is the one thing an agent could still get wrong when interpreting the response.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies a parameterless call by embedding the asset (FLIP) in the fixed URL.

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 a specific resource (Chainflip / FLIP) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. In a sibling set of hundreds of near-identical `buy_coin_*` / `buy_tok_*` price endpoints, the asset name embedded in both the tool name and the description is what lets an agent pick this one without opening a schema.

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: an agent infers 'call this when you want the FLIP spot price.' There is no explicit when-to-use statement, no when-not, and no comparison to adjacent siblings such as `buy_tvl_chainflip` (Chainflip TVL) or `buy_crypto_price` (general price lookup), which are the plausible alternatives an agent would weigh.

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