Skip to main content
Glama

SouthPow crypto & market data

buy_tok_POLYX

Paid. Polymesh (POLYX) 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/POLYX.

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

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, the description carries the full burden, and it does add real value: cost ($0.01 USDC), accepted chains (Base or Solana), no auth requirement, and a no-charge guarantee for failed calls — these are exactly the traits an agent cannot get from the empty schema. It still omits what a successful response looks like beyond a field list, freshness/caching semantics, and what constitutes a 'failed call', leaving the payment behavior partly underspecified for a paid 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?

Five short clauses, front-loaded with what the tool returns, followed by price, access terms, failure policy, and the endpoint URL — every sentence carries information. The staccato fragments ('Paid.') read slightly telegram-style, but nothing is wasted and nothing is buried.

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 price lookup, the description covers the payload fields, the cost and chains, the auth situation, and the failure billing rule — enough for an agent to decide and call correctly. The remaining gap is the buy_tok vs buy_coin vs buy_crypto_price relationship, which matters a lot given the sibling explosion but is not needed to execute this specific call.

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 for a parameterless tool applies. The URL hint confirms the token is fixed, which reinforces that no arguments are needed.

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 specific resource and payload — 'Polymesh (POLYX) price: live USD price, 24h change and market-cap rank' — so an agent knows exactly which asset and which fields it gets. It falls short of a 5 because it never explains how this differs from the hundreds of near-identical siblings (buy_coin_*, buy_crypto_price, other buy_tok_* entries); the 'Paid.' lead-in and the buy_ prefix are the only signals that this is a purchase.

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 conditions are implied rather than stated: the payment terms and 'No account, no API key' tell the agent this is a pay-per-call endpoint with no prerequisite setup, which is useful. However, there is no explicit when-to-use guidance and no named alternative (e.g. buy_crypto_price for a broader quote), so routing between this and its many siblings is left entirely to the agent's inference.

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