Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JTRSY

Paid. Janus Henderson Anemoy Treasury Fund (JTRSY) 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/JTRSY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the important commercial traits: $0.01 USDC on Base or Solana, no account or API key, and failed calls are not charged. It stops short of describing response shape, latency, caching, or what a partial/failed response looks like, so a caller still has unknowns at invoke time.

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-loads the 'Paid' flag, then purpose, then price/rails, then auth/failure policy, then endpoint. Each clause carries distinct information. The bare URL is marginal value for an agent but defensible as a provenance/debug aid.

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?

With no output schema and no annotations, the description must convey both what comes back and what it costs, and it does: three named return fields, price, payment chains, and the no-charge-on-failure guarantee. What is missing is pagination/refresh behavior and whether the quote is spot or delayed, which is a modest gap for a single-asset price tool.

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 of 4 applies; the description correctly avoids inventing parameter discussion.

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?

Names the exact asset (Janus Henderson Anemoy Treasury Fund, ticker JTRSY) and enumerates the payload: live USD price, 24h change, market-cap rank. That level of specificity is what separates it from the hundreds of other buy_tok_* siblings. It never states a verb like 'fetch' or 'returns', but the data points imply retrieval unambiguously.

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 is implied by the asset name: call this when you need a JTRSY quote. There is no explicit when-not guidance and no pointer to any alternative (e.g. free price routes or the adjacent buy_tok_DEJTRSY), which matters in a catalog this dense where near-duplicate tickers exist.

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