Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UNP

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

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

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 payment chains, that no account or API key is needed, and that failed calls are not billed. The remaining gap is that it does not describe the response shape or error behavior, but the cost and auth profile are unusually explicit for a paid endpoint.

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?

Roughly three short sentences, front-loaded with 'Paid.' and then the data delivered, which are the two things an agent needs first. The payment and URL details are terse and earn their place, though the telegraphic style ('Paid.') is slightly clipped.

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 zero-parameter price lookup with no output schema and no annotations, the description names the returned fields (USD price, 24h change, market-cap rank), the cost, and the access requirements. About the only thing missing is the response format, which is minor for an endpoint this simple.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies a fixed, parameterless endpoint scoped to UNP.

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?

States a specific verb and resource: returns live USD price, 24h change, and market-cap rank for Unipoly (UNP). An agent immediately knows what data comes back. It does not, however, explain how this differs from the large family of buy_coin_* and buy_tok_* siblings, so sibling differentiation is left to the tool name 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?

The description gives payment and access context ('$0.01 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged') which tells the agent what invoking costs and requires. It never states when to choose this over an alternative, e.g. whether buy_coin_UNP or buy_crypto_price covers the same asset, so selection guidance is only implied by the tool name.

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