Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TCY

Paid. THORChain Yield (TCY) 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/TCY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 behavioral burden and does so reasonably: it discloses the monetization model (paid, $0.01), the accepted payment chains (Base or Solana), the absence of auth requirements, and the billing behavior on failure ('Failed calls not charged'). It also enumerates the returned data points. It stops short of rate limits, latency, or response format, which is a real but minor gap given the tool takes no parameters.

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 and short: the asset name and payload come first, then pricing, then access terms. Every sentence carries distinct information. The trailing raw URL is the weakest element — it is a detail an agent cannot use — but it is only one clause.

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 tool, the description covers the things that actually matter for invoking it correctly: what the data is, what it costs, where to pay, and that failures are not billed. Absent an output schema, it helpfully lists the three returned metrics. Only return-format and throttling details are missing.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent arguments and instead spends its space on cost and payload.

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 asset (THORChain Yield / TCY) and the exact payload: live USD price, 24h change, market-cap rank. That is a concrete verb-plus-resource statement an agent can act on. It does not distinguish itself from the ~1000 sibling token endpoints (e.g. buy_coin_TCY vs buy_tok_TCY) beyond the token symbol in the name, so sibling routing is left implicit.

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 useful decision context — it costs $0.01 USDC on Base or Solana, needs no account or API key, and failed calls are free — which is exactly the information needed to decide whether calling is worth it. However, there is no explicit statement of when to use this versus an alternative endpoint for the same asset, and no prerequisites beyond payment.

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