Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TRIA

Paid. TRIA/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/TRIA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 well: it discloses the price ($0.05 USDC on Base), payment rail, zero-auth requirement, failure-billing policy, source venues, and the exact endpoint URL. It omits rate limits, latency, and error-response behavior, keeping it short of a 5.

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?

Four dense fragments with zero filler: cost first, then payload contents, then prerequisites/billing, then the URL. Front-loading the paid nature ahead of the data description is exactly the right ordering for an agent deciding whether to call.

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, no-output-schema fetch tool this is nearly complete — data fields, sources, price, auth, and failure billing are all stated. The only residual gap is the concrete response shape (JSON structure, units, timestamp) and error signaling, which the absent output schema leaves undocumented.

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 input schema has zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description usefully confirms that no account or API key input is needed, which is the only parameter-adjacent question an agent could have.

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?

States a specific resource and scope: TRIA/USD live price with enumerated fields (last price, 24h open/high/low, % change, 24h and 30d volume) and named data sources (Coinbase Exchange, Kraken cross-check). The ticker in the name plus the explicit field list lets an agent separate this from the generic buy_crypto_price sibling without opening any schema.

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?

Gives clear operating context: it is a paid call at $0.05 USDC on Base, needs no account or API key, and failed calls are not charged — which tells an agent the cost/prerequisite posture. It does not explicitly say when to prefer this over buy_crypto_price or other price siblings, nor any when-not conditions.

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