Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NEWT

Paid. NEWT/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/NEWT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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: it discloses the $0.10 USDC cost on Base, that no account or API key is needed, that failed calls are not charged, and that prices come from Coinbase Exchange with a Kraken cross-check. Missing only latency/response-shape details, which the field enumeration partly covers.

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 single dense sentence chain with the most decision-relevant fact (Paid) front-loaded and the returned fields immediately after. The raw endpoint URL is arguably dead weight for an agent that cannot construct HTTP calls, a minor inefficiency.

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?

With no input parameters and no output schema, the description must convey both what comes back and the commercial terms, and it does both: it lists the returned metrics and the payment/auth model. An agent has enough to decide and invoke correctly, with only source-freshness or latency 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 implies a parameter-free call and adds the endpoint URL, though no parameter meaning is needed or expected.

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 scope (NEWT/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It does not explicitly contrast with sibling tools such as buy_crypto_price, but the ticker-specific framing makes the target asset unambiguous.

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 only implied: an agent infers it should call this when it needs NEWT pricing. There is no statement of when NOT to use it, nor any pointer to the generic buy_crypto_price or other siblings for cross-asset queries, which matters in a list of hundreds of near-identical tools.

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