Skip to main content
Glama

SouthPow crypto & market data

buy_tok_COAI

Paid. ChainOpera AI (COAI) 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/COAI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden and does a good job on the commercial terms: price per call, accepted chains (Base or Solana), no account or API key, and the important guarantee that failed calls are not charged. It omits freshness/latency, rate limits, and what a successful versus failed response looks like, so the picture is incomplete for a paid, non-annotated tool.

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?

Six short fragments, front-loaded with 'Paid.' and then the data content, cost, access requirements and endpoint. Nothing is wasted, though the telegraphic style and inline URL make it read more like a price tag than a specification.

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 what is returned, what it costs, how to pay, and the failure-charging policy — enough for an agent to decide and call correctly. The remaining gaps (latency, error shapes) are secondary given the simplicity of the operation.

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 and the baseline of 4 applies. The token identity is baked into the tool itself, which is consistent with the empty schema.

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 names the exact resource (ChainOpera AI / COAI) and specifies the payload: live USD price, 24h change and market-cap rank. It is clearly a single-asset price lookup, though it does not differentiate itself from the generic buy_crypto_price tool or explain the split between the buy_coin_* and buy_tok_* families.

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 rather than stated: an agent can infer this is the way to fetch a COAI quote, and the '$0.01 USDC' line signals it is a paid call worth reserving for a specific need. There is no explicit when-not guidance and no named alternative such as buy_crypto_price or buy_coin_*, which matters in a sibling set this large.

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