Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NEIRO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose several genuinely important traits — the tool is paid, the price ($0.01 USDC), accepted chains (Base or Solana), no auth required, and failed calls are not charged. It stops short of describing rate limits, latency, or what a successful vs. failed response looks like, so the coverage is meaningful but partial for a paid call.

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?

Front-loaded with what is returned, then payment and auth terms, then the endpoint. Every clause carries information an agent needs, and there is zero padding.

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 output schema, the description correctly compensates by naming the returned fields, and it fully covers the payment and auth model for a paid tool. The remaining gap is sibling differentiation within a very large price/coin family, which the description never addresses.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The embedded endpoint URL is a minor bonus for transparency but adds no parameter meaning.

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?

Names a specific verb and resource: 'Neiro (NEIRO) price' with the returned fields spelled out (live USD price, 24h change, market-cap rank). It is clear what the tool does, but it never explains how it differs from the mass of buy_coin_* and buy_crypto_price siblings, leaving the agent to infer that this is the token-price variant rather than the coin-list variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance and no named alternative, despite hundreds of near-identical price/coin siblings. The only usage-relevant signals are cost and auth ('$0.01 USDC', 'No account, no API key'), which are useful but are not routing guidance.

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