Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NEXO

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

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

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 paid model, exact cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. That is meaningful behavioral context beyond a bare read of the name, though it doesn't state rate limits or latency.

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?

The description is short and front-loaded: the paid cost appears first, then the returned fields, then payment rails, then the endpoint. It is telegraphic to the point of terseness, and the raw URL duplicates routing metadata an agent may not need, but no sentence is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description names the three returned values (live USD price, 24h change, market-cap rank), and it covers the payment, custody and failure-cost model that an agent must account for before calling. For a zero-parameter single-value tool, nothing essential is 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 nothing for the schema to document and nothing the description must compensate for. The description appropriately spends its words on payment mechanics instead of inventing parameter semantics.

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 states a concrete verb and resource (live USD price, 24h change, market-cap rank for NEXO), so the agent knows exactly what data comes back. It does not distinguish this per-token tool from the generic buy_crypto_price or the nearby buy_coin_NEX sibling, leaving the token-specific routing 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?

"Paid." and the $0.01 price signal that a cost is involved, and the payment rails are named, which is implied guidance about when this is appropriate. However, it never states when to prefer a free or alternative price tool, nor any exclusions, so the when-to-use decision is left to 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