Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DINERO

Paid. Dinero (DINERO) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/DINERO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavioral burden and does substantial work: it discloses that the call is paid ($0.05 USDC on Base or Solana), requires no account or API key, that failed calls are not charged, and gives the endpoint URL. It doesn't describe the response payload shape or latency, but the core commercial and auth behavior is unusually well disclosed for this catalog.

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?

Terse and front-loaded: 'Paid.' immediately flags the cost model, then the payload, then pricing, then auth, then refund policy. The telegraphic fragments ('$0.05 USDC on Base or Solana') are efficient rather than confusing, and nothing is redundant.

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

Completeness3/5

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

For a zero-parameter paid lookup with no output schema and no annotations, the description covers cost, auth, failure billing, and the fields returned. What's missing is the response shape (field names, units, precision) and whether results are cached, which matters because there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 to misinterpret and no schema burden to compensate for. The description correctly implies no inputs are needed, but there is no parameter meaning to add beyond that baseline.

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 resource (Dinero/DINERO) and states exactly what the call returns: live USD price, 24h change, market-cap rank. The token identity in the name already distinguishes it from the large family of buy_tok_* siblings, but it never clarifies how it differs from the generic buy_crypto_price, which an agent might reasonably prefer.

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: 'buy a price quote for DINERO.' There is no statement of when to pick this over buy_crypto_price or other token-price siblings, and no note about staleness or refresh cadence. Payment terms are given, but selection guidance among alternatives is absent.

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