Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FONQ

Paid. FONQ (FONQ) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/FONQ.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does real work: it discloses that calls are paid at $0.05 USDC on Base or Solana, that no account or API key is required, that failed calls are not charged, and it gives the underlying URL. What it omits is any rate-limit, latency, or response-shape information, which matters for a paid endpoint where a wasted call costs money.

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?

Front-loaded with 'Paid.' and then the payload description, followed by cost/auth/failure terms and the endpoint. Only minor redundancy ('FONQ (FONQ)') and mild repetition between 'Paid' and the explicit price line.

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 paid lookup, the description covers cost, chains accepted, auth posture, failure billing, and the returned metrics. Without an output schema it could say more about response format, but nothing essential to calling it correctly is missing.

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 mis-specify. It usefully enumerates the data fields the response will contain, which is more than the empty schema conveys.

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?

States the resource (FONQ token) and exactly what data it returns: live USD price, 24h change, and market-cap rank. An agent can tell it is the FONQ-specific price endpoint rather than a generic one. It stops short of an explicit verb phrase like 'fetch', but the resource and payload are unambiguous.

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?

The paid nature and $0.05 USDC cost imply 'use only when you specifically need FONQ price data,' which is useful routing context. However, it never names alternatives (e.g., a generic crypto-price tool or the buy_coin_* family) or states when not to call it, leaving the agent to infer selection criteria.

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