Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CHI

Paid. Chili Coin (CHI) 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/CHI.

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

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?

No annotations exist, so the description carries the full burden and largely meets it: it discloses the price ($0.01 USDC on Base or Solana), the payment rails, that no account or API key is needed, and that failed calls are not charged. It stops short of describing the payment handshake/flow or data freshness, but the economic and failure semantics are unusually well covered.

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 with 'Paid.' and then the resource, followed by cost, prerequisites, and failure policy in tight telegraphic sentences. Nothing is padded, though the trailing raw URL is more operational trivia than decision-relevant content for an agent.

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?

With no parameters and no output schema, the description must enumerate what comes back, and it does — live USD price, 24h change, market-cap rank. Payment cost, chains, and refund-on-failure policy are all present; only response shape specifics (types, units, timestamp) are absent, which is a minor gap for a zero-arg read.

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; baseline is 4. The description correctly frames this as a fixed, single-asset endpoint rather than implying any filters or options.

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?

States a concrete verb-plus-resource: live USD price, 24h change and market-cap rank for Chili Coin (CHI). An agent can tell exactly which asset and which fields this returns, though it never references the near-identical siblings (buy_coin_CHI, buy_crypto_price) to explain why one should pick this one.

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 by the 'Paid.' prefix and the named data fields — there is no explicit when-to-use or when-not-to-use statement, and no routing to the many sibling price tools. The explicit 'No account, no API key' line does help an agent decide it can call this without setup.

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