Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NOW

Paid. ChangeNOW (NOW) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/NOW.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the important traits: it is a paid call, costs $0.01 USDC on Base or Solana, needs no account or API key, and failed calls are not charged. What it omits is equally relevant for a paid endpoint - rate limits, whether invocation is via the listed URL or the MCP call itself, and any staleness/latency expectations.

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?

Tight and front-loaded - 'Paid.' and the token identity lead, followed by payload contents, price, auth requirements and failure policy, with the endpoint last. Nearly every clause carries information; only the bare URL could be considered optional context.

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-annotation, no-output-schema tool, the description covers what it returns, what it costs, how to pay, and how failures are billed, so an agent has enough to decide and invoke. It lacks only guidance on the alternative general-purpose price sibling and any note on response freshness.

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 no parameter meaning to add and the baseline of 4 applies. Nothing in the description conflicts 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?

Names the specific resource and its ticker (ChangeNOW (NOW) price) and enumerates the exact returned fields: live USD price, 24h change, market-cap rank. That is well beyond a restatement of the name. It stops short of differentiating this from the sibling generic tool buy_crypto_price or from the buy_coin_* family, which is the only reason it is not 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 only implied: an agent can infer it should call this when it needs the NOW spot price. There is no explicit when-not-to-use and no mention of the near-identical sibling buy_crypto_price, so an agent cannot tell from this text whether this per-token tool is preferable to the general price tool.

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