Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AR

Paid. Arweave (AR) 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/AR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 load and does a decent job: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The main omissions are rate limits and how the payment handshake is actually performed, which matter for an agent deciding whether it can call this autonomously.

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?

It is a compact set of fragments that is front-loaded with the key fact ("Paid."), then the payload, then cost and access terms. Every clause carries information, though the telegraphic style makes it read as a stack of facts rather than a structured sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There are no parameters, no annotations, and no output schema, so the description must cover both the payment mechanics and the return shape; it does the return shape (price, 24h change, rank) and the cost well. It stops short of explaining how the USDC payment is actually settled (e.g. an HTTP 402 challenge vs. a pre-funded balance), which is the single detail an agent needs before invoking a paid endpoint.

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. No parameter information is missing or misstated.

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?

The description names a specific resource and asset (Arweave / AR) and states exactly what data comes back: live USD price, 24h change, market-cap rank. That is enough to distinguish it from the other per-asset buy_tok_* tools. It does not, however, clarify how it differs from the near-identical buy_coin_AR or buy_crypto_price siblings, which is the one real ambiguity in this catalogue.

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?

Implicit usage is clear (you call it when you want an AR price), and the pay-per-call framing sets a cost context. But there is no explicit when-to-use/when-not guidance and no pointer to the sibling tools that overlap with it, leaving the agent to infer which AR price tool to pick.

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