Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ARB

Paid. ARB/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ARB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 burden and does well: it discloses cost ($0.25 USDC on Base), authentication (no account or API key), billing policy (failed calls not charged), and data sources (Coinbase Exchange with Kraken cross-check). It leaves out rate limits, latency expectations, and a precise definition of 'failed call' (e.g., HTTP errors vs. empty responses).

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?

The description is dense but efficiently front-loads key information: payment status, data fields, cost, access requirements, and endpoint. It uses short phrases and avoids repetition. Minor clutter from the trailing URL and the fragment 'Paid.' is acceptable but slightly reduces flow.

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?

For a zero-parameter paid API with no annotations or output schema, the description covers cost, auth, billing, and data sources, which is substantial. However, it omits critical invocation details: HTTP method, how payment is actually executed (e.g., automatic vs. manual USDC transfer), and the response format. These gaps could confuse an agent attempting to call the 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 has zero parameters, so the baseline is 4. The description adds no parameter semantics because there are none, and the provided URL is an endpoint rather than an input parameter. Schema coverage is 100%, so nothing further is needed.

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 explicitly states the resource and data fields: 'ARB/USD live: last price, 24h open/high/low, % change, 24h and 30d volume.' It is clearly a price-feed tool for ARB, distinguishable from sibling coin tools by the token symbol and specific fields. However, it lacks an explicit action verb (e.g., 'Get') and does not directly differentiate from the generic buy_crypto_price sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention the generic buy_crypto_price tool or any conditions for selecting ARB-specific data. Usage is only implied by the token symbol and listed fields.

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