Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ACRDX

Paid. Anemoy Tokenized Apollo Diversified Credit Fund (ACRDX) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ACRDX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a decent job: it discloses the paid model, the exact price and payment chains, that no authentication is needed, that failures are not billed, and the underlying endpoint URL. It omits rate limits, latency, and freshness/caching behavior, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short, front-loaded fragments with no filler: the 'Paid.' lead sets expectations immediately, then subject, payload, price, access terms, and endpoint. Every element is load-bearing for an agent deciding whether to call.

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 price lookup, the description covers what is returned and what it costs, which is enough to call correctly. It would be complete at 5 with a note on response shape or data freshness, but nothing critical is missing.

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 the baseline is 4 and there is no parameter semantics to add. The description correctly implies the ticker is baked into the endpoint rather than passed as an argument.

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?

The description names the exact resource (Anemoy Tokenized Apollo Diversified Credit Fund, ticker ACRDX) and enumerates the returned fields: live USD price, 24h change, and market-cap rank. Against hundreds of sibling buy_tok_* tools, the ticker in the first sentence makes the target 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?

It conveys practical usage conditions — $0.05 USDC on Base or Solana, no account or API key required, failed calls not charged — which helps an agent decide whether it can invoke it. However, it never states when to prefer this over alternatives such as buy_crypto_price, buy_tok_ACRED, or the buy_cp_rwa category tool, nor any exclusions.

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