Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OTFY

Paid. Obligate Trade Finance Yield (OTFY) 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/OTFY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does well on commercial behavior: price ($0.05 USDC on Base or Solana), no account or API key required, and failed calls not charged, which is genuinely useful non-structural context. It says nothing about response format, payment flow (x402 handshake), latency, or freshness guarantees.

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.' followed by the payload contents, then terms, then endpoint — a sensible order with no filler. The telegraphic fragment style ('$0.05 USDC on Base or Solana. No account, no API key.') is compact but slightly choppy.

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 price lookup with no annotations and no output schema, the description covers cost, payment rails, auth requirements, refund behavior, returned fields, and the underlying URL — close to what an agent needs to call it. Only output shape and data freshness are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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, but the description uses its space to name output fields rather than confirm there is nothing to supply. That leaves it at minimum-viable-plus rather than adding meaning the empty schema cannot.

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?

Names the specific resource (OTFY price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. The token suffix in the name plus the spelled-out expansion 'Obligate Trade Finance Yield' lets an agent distinguish this from the hundreds of sibling buy_tok_* tools. It never explains how it relates to buy_crypto_price, which appears to serve a similar role.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as buy_crypto_price or search_facts for the same data. Usage is only implied by the field list. With hundreds of near-identical siblings, a routing sentence would materially help selection.

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