Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FIDD

Paid. Fidelity Digital Dollar (FIDD) 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/FIDD.

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

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 burden, and it discloses the important traits: this is a paid call at $0.05 USDC on Base or Solana, requires no auth, and failed calls are not charged. Missing rate limits, latency, and response shape, but the transactional behavior an agent needs before spending money is covered.

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?

Telegraphic but every clause earns its place: price disclaimer first, then payload, then cost/rails, then auth and failure policy, then endpoint. Nothing redundant.

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 single-asset, zero-parameter paid lookup with no output schema, the description tells the agent what it costs, how to pay, that auth is unnecessary, what failure costs, and what data comes back. Endpoint URL is also included, filling the gap left by absent structured metadata.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not waste effort restating a schema that is empty.

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 a concrete verb (buy/fetch price) plus the exact asset and the three returned fields (USD price, 24h change, market-cap rank). Naming the specific ticker plus the human-readable name distinguishes it from the buy_coin_* and buy_crypto_price siblings, though it never explicitly contrasts with buy_crypto_price.

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?

Gives operational context (no account, no API key) but no guidance on when to pick this over buy_crypto_price or the buy_coin_FIDA sibling. Usage is only implied by the asset name; there are no exclusions or alternative routing.

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