Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ARKM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/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 a respectable job: it discloses the paid nature ($0.002 USDC on Base), that no account or API key is required, that failed calls are not charged, and that prices come from Coinbase with a Kraken cross-check. It does not say whether the charge occurs before or after a successful fetch, whether there are rate limits, or how stale the quotes can be — meaningful gaps for a metered paid endpoint.

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?

Four terse fragments and a URL, front-loaded with the payload fields first and commercial terms second. Every clause carries information — data fields, sources, price, prerequisites, billing policy, endpoint — with no filler.

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

Completeness5/5

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

There is no output schema, so the description must enumerate return values, and it does so exhaustively (last, open, high, low, % change, 24h and 30d volume). Combined with cost, auth-free access, and billing policy, an agent has everything needed to decide and invoke correctly.

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 is 4; the description correctly adds no parameter commentary because there is nothing to parameterize. The ARKM symbol is fixed in the endpoint, which is implicit but consistent with the empty schema.

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 states precisely what is returned: ARKM/USD live last price, 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The token identity (ARKM) is the only differentiator among ~300 near-identical buy_coin_* siblings, and it is carried by the name rather than the prose, which keeps this just short of a 5.

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: you call this when you need ARKM spot data. There is no explicit when-to-use or when-not, and no pointer to a sibling alternative (e.g. buy_crypto_price) for multi-asset or different-quote needs. A reader can infer the context, but nothing routes them.

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