Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ACRED

Paid. Apollo Diversified Credit Securitize Fund (ACRED) 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/ACRED.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 price, payment chains and currency, that no authentication is required, that failed calls are not charged, and even the endpoint URL. It stops short of describing response shape or latency, which keeps it off 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?

Roughly three short sentences, front-loaded with the paid flag and the asset identity, then cost and access terms. It is telegraphic but every clause carries operational information; the trailing URL is arguably redundant with the tool itself.

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 entry covers what is returned, what it costs, and how payment/auth works. The only missing piece is any notion of response format or freshness/latency, which a caller of a live price feed might reasonably want.

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 schema baseline of 4 applies. The description correctly conveys that a single fixed asset is queried without any input.

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 (Apollo Diversified Credit Securitize Fund / ACRED) and the specific payload: live USD price, 24h change, and market-cap rank. An agent can tell this returns price data rather than, say, yield data from the many buy_yields_protocol_* siblings, though it never explicitly contrasts itself with the buy_coin_* / buy_tok_* families.

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?

Conveys practical invocation context (paid, $0.05 USDC on Base or Solana, no account or API key) that tells an agent how it can be called, but offers no explicit when-to-use/when-not guidance and names no alternative tool for the same asset data.

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