Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FTRB

Paid. Faith Tribe (FTRB) 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/FTRB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 does most of it: it discloses the cost ($0.01 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged — unusually good disclosure for a paid endpoint. It stops short of rate limits, latency, or the exact response shape (JSON keys, quote currency), which are the remaining behavioral gaps.

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?

Front-loads 'Paid.' so the cost signal is impossible to miss, then ticker, returned fields, price/rails, auth model, failure policy, and endpoint — each fragment carries distinct information and none is 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 trivial zero-param lookup, an agent has everything needed to decide and call: cost, payment method, auth, failure semantics, and the three data fields returned. Without an output schema, slightly more detail on response format (key names, fiat denomination, timestamp) would fully close the gap.

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 no parameters, so there is nothing the description must disambiguate beyond what the schema already shows. Baseline for a zero-parameter tool applies without any countervailing evidence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource (Faith Tribe / FTRB) and the payload it returns: live USD price, 24h change, market-cap rank. Among the hundreds of buy_tok_<SYMBOL> siblings, the ticker in the description is the discriminator and it is stated unambiguously.

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 only implied — an agent can infer 'call this when you need the FTRB spot price' — but there is no explicit guidance on when to prefer a sibling like buy_crypto_price or a category bundle, and no exclusions. The payment terms describe how to transact, not when to choose this tool over an alternative.

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