Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FT

Paid. Flying Tulip (FT) 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/FT.

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

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 at all, the description carries the full burden and does a solid job: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and the important non-obvious billing behavior that failed calls are not charged. It omits response shape details such as units, timestamp/currency of the price, and whether the value is cached or real-time despite claiming 'live'.

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?

Four short, dense sentences with zero filler: paid flag and asset/scope first, then the returned fields, then cost and payment rails, then auth and billing caveats. Each sentence carries distinct decision-relevant information.

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 tool, the description covers what an agent needs to decide to call it: what data comes back, what it costs, how to pay, and that there is no signup. It falls slightly short on response specifics (units, quote currency, freshness) that would matter since no output schema exists to fill the gap.

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 no parameter meaning to convey and the baseline applies. Nothing in the description misleads about inputs, and the absence of parameters is consistent with a fixed single-asset price endpoint.

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?

The description names a specific resource (Flying Tulip / FT) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. The token-specific tool name plus the explicit resource makes it trivially distinguishable from the hundreds of buy_coin_*/buy_tok_* siblings, and the endpoint URL confirms the single asset covered.

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 infers 'call this when you need FT's price.' The description does give practical invocation context (paid, no account, no API key, failures not charged), but it never names an alternative or a when-not condition — notably it does not mention the buy_coin_* / buy_crypto_price siblings an agent could use for broader price lookups.

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