Skip to main content
Glama

SouthPow crypto & market data

buy_tok_F

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

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

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 behavioral burden and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged—all decision-relevant facts an agent cannot get from structured fields. It stops short of stating rate limits, latency, or the exact 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.

Conciseness5/5

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

Roughly three short sentences, front-loaded with cost and subject, then constraints, then the endpoint URL. Every clause carries usable information—price, billing, auth, failure policy—with no padding.

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-param, no-output-schema, annotation-free tool, the description supplies what matters: what data comes back, price, payment rails, auth expectations, and failure billing. Only the response encoding and any rate limits are unaddressed, which are minor gaps at this 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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline applies. The description does not waste space restating an empty schema.

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 states a specific resource and payload: SynFutures (F) live USD price, 24h change, and market-cap rank. Naming the exact asset distinguishes it from the hundreds of sibling buy_tok_*/buy_coin_* tools, though it never contrasts itself with the general buy_crypto_price sibling. Purpose is clear without opening anything else.

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 by the paid-price framing and the named asset, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the general buy_crypto_price alternative that could serve overlapping needs. The practical constraints it does give ($0.01, no account, no API key) help an agent decide whether to call it at all.

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