Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ASM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 that the call is paid ($0.10 USDC on Base), that no account or API key is required, that failed calls are not charged, and which exchanges the data comes from. Not covered: response shape/pagination, latency, and any freshness or rate-limit guarantees.

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?

Front-loaded with 'Paid.' so the cost signal lands first, then data scope, then payment mechanics, then the endpoint. It is telegraphic and dense rather than verbose, though the final bare URL sentence is slightly abrupt and the field list could be grouped more readably.

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-param, no-output-schema, unannotated paid endpoint, the description supplies the essentials an agent needs: what data comes back, what it costs, that no auth is needed, and that failures are free. Only the concrete response shape and freshness guarantee are left unstated.

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 introduces no parameter semantics and instead spends its words on cost, sourcing, and return fields, which is the right allocation.

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 the exact resource and pair (ASM/USD) and enumerates the fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. That is enough to distinguish it from the hundreds of sibling buy_coin_<TICKER> tools, though the verb is only implied by the ticker rather than stated directly.

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?

There is no when-to-use or when-not guidance. It never mentions the aggregate alternative buy_crypto_price or explains when an agent should pick a ticker-specific tool over it, and it does not say whether repeated polling is expected or discouraged despite the per-call charge.

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