Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XNY

Paid. Codatta (XNY) 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/XNY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 monetary cost, the accepted payment chains, that no account or API key is required, and that failed calls are not charged — all behaviors an agent cannot infer from an empty schema. It stops short of stating rate limits, latency, or data freshness beyond 'live'.

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?

Five telegraphic fragments, front-loaded with the payment flag and the data payload, then cost, then conditions, then endpoint. Every clause carries distinct, non-redundant information and nothing is repeated from structured fields.

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 parameterless paid read with no output schema, the description covers what is returned, what it costs, how to pay, auth requirements, and failure billing — enough for an agent to decide and invoke. The missing piece is differentiation from the near-identical sibling price tools, which matters a lot at this catalog size.

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 the baseline is 4 and there is nothing for the description to clarify on that axis. The description correctly implies no arguments are needed by presenting the token as baked into the call.

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 a specific resource and verb: 'Codatta (XNY) price: live USD price, 24h change and market-cap rank.' An agent immediately knows exactly what payload comes back. It does not, however, differentiate this from the many sibling variants (e.g. buy_crypto_price or buy_coin_XNY), leaving the agent to infer the distinction from the tool name alone.

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: this is the XNY-specific price call, and the payment rails ($0.01 USDC on Base or Solana) hint at when it is affordable to call. There is no explicit 'use this instead of X when Y' routing against the generic buy_crypto_price or buy_coin_XNY siblings, which is the main gap for a 500-sibling family.

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