Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ARC

Paid. AI Rig Complex (ARC) 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/ARC.

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

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 so well on the commercial side: it discloses a fixed price of $0.01 USDC payable on Base or Solana, that no account or API key is needed, and that failed calls are not charged. What it omits is freshness or caching behavior of the quoted price and any rate limiting, which matters for a market-data call.

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?

Sentences are short, front-loaded with the 'Paid.' flag, then purpose, then cost and billing terms, then the endpoint. Every clause carries distinct information with no repetition.

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?

There are no inputs and no output schema, so the description must carry the return shape itself, and it enumerates the three key fields (USD price, 24h change, market-cap rank). It stops short of describing the response structure or units/format for the change value, which leaves a small gap for a zero-schema 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 the baseline applies; there is no parameter meaning for the description to add. The description correctly implies the token is baked into the endpoint via the included URL, which is the only semantically relevant '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 asset ('AI Rig Complex (ARC)') and the specific data returned ('live USD price, 24h change and market-cap rank'), so an agent can distinguish it from the nearby single-token siblings like buy_tok_AR, buy_tok_ARARA, or the generic buy_crypto_price without opening a schema.

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 agent must infer that this is the tool to call when it wants ARC-specific pricing and that alternatives such as buy_crypto_price or buy_coin_* exist for other purposes. It does clarify payment rails and that no account or API key is required, which removes onboarding friction, but there is no explicit when-not-to-use guidance.

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