Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NOPAL

Paid. Nest BlackOpal LiquidStone II Vault (NOPAL) 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/NOPAL.

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

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 so well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. Missing rate-limit or latency context keeps it short of a 5.

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?

Front-loaded with 'Paid.' then the data payload, then payment mechanics and the URL. Nearly every sentence earns its place; the only slight redundancy is repeating the vault name and symbol pairing, which is still useful identification.

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?

For a zero-parameter, no-output-schema price lookup, the description is complete: it names the asset, enumerates the returned fields, states the cost and payment rails, and gives the endpoint. Nothing an agent needs in order to invoke it correctly is absent.

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 and the schema is empty, so the baseline is 4. The description correctly implies a parameter-free call keyed to a single fixed asset, leaving nothing ambiguous for the agent to supply.

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 specific resource (NOPAL / Nest BlackOpal LiquidStone II Vault) and exactly what data comes back: live USD price, 24h change, and market-cap rank. It clearly reads as a price-quote tool, though it does not distinguish itself from near-neighbors like buy_coin_* or buy_tok_OPAL, which an agent must infer from the symbol 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 only implied: an agent can infer 'call this to get the NOPAL quote.' There is no explicit statement of when to prefer this over the sibling coin/price tools or when not to call it, so routing across the very large sibling set remains guesswork.

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