Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NYC

Paid. NYC (NYC) 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/NYC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the call is paid at $0.01 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged — the key cost/failure semantics an agent needs. It omits freshness/latency, rate limits, and whether payment is settled per-call or batched.

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 the 'Paid.' marker, then payload, then price/rails, then payment-free guarantees, then the endpoint URL — dense and telegraphic with no filler. The 'NYC (NYC)' phrasing is slightly redundant and the bare URL adds little for an MCP caller, but nothing is bloated.

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?

For a zero-parameter, no-output-schema price tool, the description already names the returned fields (price, 24h change, market-cap rank) and fully covers cost, payment rails, and failure charging. An agent has everything required to decide to call it and what it will pay.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description efficiently specifies the fixed asset (NYC) in place of a parameter, which is the only semantic an agent needs.

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?

States the specific resource (NYC token) and the exact payload (live USD price, 24h change, market-cap rank), which tells an agent precisely what it gets. It does not differentiate from the hundreds of sibling buy_tok_* / buy_coin_* price endpoints or mention a generic alternative like buy_crypto_price, so the agent must infer from the name that this covers only the NYC symbol.

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 guidance: nothing says to pick this only when the target asset is NYC, or to use buy_crypto_price/buy_coin_* otherwise. The payment details imply this is a paid single-asset lookup, but selection logic versus alternatives is left entirely to inference from the tool name.

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