Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NALPHA

Paid. Nest Alpha Vault (NALPHA) 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/NALPHA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted chains, that failed calls are not charged, and that no auth is required. The gaps are secondary but real - no rate limit, no freshness/caching statement, no note on what a failure response looks like before the charge is waived.

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-loading with "Paid." is exactly right - the cost is the first thing an agent must know. The sentence is dense with no filler, though the trailing raw URL is somewhat redundant with the tool wiring itself and slightly fragments the structure.

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 no-parameter, no-annotations, no-output-schema tool, the description covers the essentials an agent needs: what it returns, what it costs, which chains, and that failures are free. It stops short of describing the response shape or data currency, which matters because no output schema exists to carry that information.

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 description to disambiguate; the statement "No account, no API key" usefully confirms that no credential or asset-identifier argument is needed. Baseline 4 for a 0-param tool is appropriate.

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 issuer ("Nest Alpha Vault (NALPHA)") and enumerates exactly what the payload contains: live USD price, 24h change, and market-cap rank. That is far more than the tautological name restatement. It loses a point only because among hundreds of buy_tok_* siblings it never states the selection rule versus a generic lookup like buy_crypto_price.

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 context is implied by the payment disclosures ("Paid... $0.01 USDC on Base or Solana. No account, no API key."), which tells the agent the preconditions for calling. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternative price tool an agent should pick for non-NALPHA assets.

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