Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TIA

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

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

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 supplied, the description carries the full burden and does a good job: it discloses cost ($0.25 USDC on Base), that no account or API key is needed, that failed calls are not charged, and which exchanges source the data. It stops short of describing the payment mechanism (e.g. how the USDC charge is settled), latency, or response format.

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?

Compressed to a single dense passage with zero filler: data scope first, then sources, then price, then auth/failure terms, then endpoint. Every clause conveys operational information an agent needs before calling a paid endpoint.

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 data tool with no annotations and no output schema, the description covers cost, auth, failure policy, data provenance, and return fields — enough to call it correctly. Only the response envelope and settlement mechanics are left unstated.

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; the baseline applies. The description's field list instead helps set expectations about the payload, which is a reasonable substitute.

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 makes clear the tool returns live TIA/USD market data with an enumerated field list (last price, 24h OHLC, % change, 24h/30d volume) from named sources. It is specific enough to distinguish from unrelated siblings, though the name 'buy_coin_TIA' implies purchasing the token while the description describes only a price feed, and that gap is never reconciled.

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 implied by the data being offered (live TIA price), but there is no explicit statement of when to prefer this over siblings such as buy_crypto_price or the generic buy_coin_* variants. No prerequisites or exclusions are given, leaving the agent to infer the choice from the ticker in the tool name.

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