Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AMZNX

Paid. Amazon xStock (AMZNX) 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/AMZNX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses the paid model, the exact price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing the response shape or the data's refresh latency, which is the main remaining behavioral unknown.

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?

Information is front-loaded — payment status first, then what you get, then cost and access requirements. The trailing raw URL is somewhat extraneous to an MCP caller and the leading "Paid." fragment is terse, but nothing is padded or redundant.

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-param paid price lookup with no output schema, the definition covers what an agent needs to commit: subject, cost, chain, auth requirements, billing on failure, and endpoint. Only the return format and freshness of the quote are left unstated.

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 description makes clear the ticker is baked into the endpoint. There is nothing a caller must supply, so no parameter semantics are required beyond confirming no inputs are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Amazon xStock (AMZNX) price: live USD price, 24h change and market-cap rank" states a specific resource (the AMZNX price feed) and enumerates the exact fields returned. The ticker plus "xStock" makes it unambiguously distinct from the hundreds of buy_tok_* siblings and from 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?

The description implies the usage context (an agent needing AMZNX spot price) and discloses the cost barrier up front, which helps an agent decide whether to call. However, it never states when to prefer this over buy_crypto_price or a neighboring token tool, and gives no guidance on caching or repeated calls despite the per-call charge.

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