Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ACX

Paid. Across Protocol (ACX) 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/ACX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted payment chains, that no credentials are needed, and crucially that failed calls are not charged — a meaningful billing-safety detail. It omits rate limits and latency/response semantics, but covers the expensive parts of the behavior.

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?

Front-loads 'Paid.' as the single most decision-relevant fact, then the resource, then cost/payment mechanics, in five short clauses with zero filler. Every sentence — including the endpoint URL — earns its place for an agent deciding whether to spend 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-annotation purchase endpoint with no output schema, the description supplies what an agent actually needs: what data comes back, what it costs, how to pay, and that failures are free. Only the output shape (field formats, units) is left unspecified.

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 and the baseline of 4 applies. The enumerated fields (price, 24h change, market-cap rank) add useful framing about what a parameterless call yields.

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?

States a specific verb and resource: it retrieves the Across Protocol (ACX) price, and it enumerates the returned fields (live USD price, 24h change, market-cap rank). It does not distinguish itself from neighboring token-price siblings such as buy_crypto_price or the buy_coin_* family, so an agent must infer the tok vs. coin distinction from naming alone.

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 rather than stated: the tool is for getting an ACX price quote. The description gives strong operational context (paid, $0.05 USDC on Base or Solana, no account/API key, failed calls not charged) but never says when to prefer this over buy_coin_ACA or buy_crypto_price, 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