Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NOICE

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

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

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 at all, the description carries the full burden and does meaningful work: it declares the tool is paid, names the price and chain (USDC on Base), states no auth is needed, and specifies that failed calls are not charged — exactly the billing/error semantics an agent needs before spending money. It omits rate limits, latency, and how payment is actually transacted.

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?

Telegraphic and front-loaded — cost is the first word, data fields second, payment/auth terms third. Nearly every clause earns its place, though the raw endpoint URL adds little for an agent that invokes the tool through MCP and reads slightly as boilerplate.

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-parameter, no-output-schema, no-annotation tool, the description covers the essentials: what data comes back, what it costs, what auth is unnecessary, and how failures are billed. The main remaining gap is the payment flow itself and any rate/usage limits, which matter for a paid endpoint.

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 there is nothing for the description to disambiguate; baseline 4 applies. The field list describes outputs rather than inputs, which is a reasonable substitute given no output schema exists.

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 (NOICE/USD) and enumerates the returned fields — last price, 24h open/high/low, % change, 24h and 30d volume — so the agent knows precisely what data it gets. It stops short of explicitly stating how it differs from the hundreds of sibling buy_coin_<TICKER> tools or from buy_crypto_price, relying on the ticker in the name to do that work.

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?

It supplies real preconditions: paid at $0.05 USDC on Base, no account or API key required, failed calls not charged. What it never says is when to prefer this over buy_crypto_price or another price sibling, or what tickers are covered elsewhere, so the choice between alternatives is left implicit.

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