Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FORT

Paid. FORT/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/FORT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/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 so convincingly: cost and payment rail (USDC on Base), the no-auth/no-account model, the failure-billing policy, the upstream data sources with a Kraken cross-check, and the literal endpoint URL. These are exactly the traits an agent needs to decide whether calling is safe and worth the spend.

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?

The description is one dense, front-loaded block: the paid flag and asset lead, then returned fields, then pricing and access terms, then the URL. Every clause carries distinct information — no restatement of the name and no filler.

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 parameterless read-only lookup with no output schema, the description covers what matters: the returned metrics stand in for a missing schema, and cost, auth, and failure behavior are all explicit. The only gap is the exact response encoding and how the USDC payment is transacted, which the agent must infer.

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 for the description to disambiguate and the baseline is 4. It correctly implies the symbol is fixed to FORT rather than being passed in.

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 precisely what the call returns: last price, 24h open/high/low, percent change, and 24h/30d volume for FORT/USD, along with the data sources. It corrects the misleading 'buy_coin_' name by making clear this is a paid price-data lookup, not a purchase. It loses a point only because it does not guard against confusion with the near-identical sibling 'buy_coin_FORTH' or point to 'buy_crypto_price' for other assets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives the practical conditions an agent needs before choosing it: it is paid ($0.05 USDC on Base), requires no account or API key, and failed calls are free. What is missing is any exclusion or alternative — it never says where to go for a different symbol or which sibling to use when FORT is not the target.

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