Skip to main content
Glama

SouthPow crypto & market data

buy_tok_APYUSD

Paid. apyUSD (APYUSD) 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/APYUSD.

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

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 supplied, the description carries the full burden and does well: it discloses the $0.01 USDC cost on Base or Solana, that no account or API key is required, that failed calls are not charged, and the endpoint URL. It omits rate limits and data freshness/source, which keeps it from 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.' and the data payload, followed by cost, payment rails, no-auth note, failure policy, and endpoint. Very dense with no filler, though the telegraphic fragments read more like a price tag than prose.

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 purchase endpoint, the description supplies everything an agent needs to decide and act: what fields are returned, what it costs, how to pay, that no credentials exist, and that failures are free. Nothing material is missing at this complexity level.

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; baseline 4 applies. The fixed-token scope is already encoded in the name and the hardcoded URL path.

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 concrete resource and scope: 'apyUSD (APYUSD) price: live USD price, 24h change and market-cap rank', so the agent knows exactly what data comes back. It does not explicitly distinguish itself from near-siblings like buy_crypto_price or the buy_coin_* family, relying on the token-suffixed name to do that work.

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 'Paid.' prefix and pricing line imply 'use this only when you specifically need APYUSD spot data and are willing to pay', but there is no explicit when-to-use or when-not statement and no named alternative for a generic price lookup. Guidance is implied rather than stated.

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