Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JAAA

Paid. Janus Henderson Anemoy AAA CLO Fund (JAAA) 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/JAAA.

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

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?

With no annotations, the description carries the burden and does well: it discloses that the call is paid, 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 explaining how payment is presented or settled per call, which is the one material behavior left opaque.

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 asset identity, then cost, access terms, and URL in a compact sequence. It is telegraphic and slightly clipped ('Failed calls not charged'), but nearly every clause carries information an agent needs before spending money.

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, no-output-schema tool, it covers what is sold, what is returned, what it costs, where payment is accepted, and the endpoint. Only the mechanics of paying and the shape of a payment failure are unaddressed, which is minor at this complexity.

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 baseline applies. The description correctly conveys that the ticker is baked in rather than something the caller supplies.

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?

Names the exact asset ('Janus Henderson Anemoy AAA CLO Fund (JAAA)') and the exact payload (USD price, 24h change, market-cap rank). Against hundreds of buy_tok_* siblings, the ticker-specific naming plus fund expansion makes selection unambiguous.

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?

Implicitly routes by ticker but never says when to choose this over adjacent tools such as buy_crypto_price or buy_cp_rwa, nor what to do if you want history rather than a live price. The payment and access constraints are stated, which helps, but there is no explicit use/avoid guidance.

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