Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NIGHT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does well: it discloses that the call is paid, the exact price and accepted chains for payment, that no account or API key is required, and crucially that failed calls are not charged. It also exposes the underlying endpoint URL. Missing only rate limits and response shape/timeliness, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very tight and front-loaded: 'Paid.' leads with the most decision-relevant fact, then the returned data, then cost/payment rails, then billing policy, then endpoint. Every clause carries information an agent would act on; nothing is padding.

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, single-asset price lookup with no output schema, the description supplies the return fields, the cost, payment options and failure billing. That is nearly complete; the only shortfall is that without an output schema the precise response format (field names, numeric precision) is left implicit.

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 no input is needed (the asset is baked into the tool name and URL), and there is nothing the schema needs the description to compensate for.

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 specific asset ('Midnight (NIGHT)') and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. That is enough for an agent to distinguish it from the mass of sibling buy_tok_* tools, since the token identity is the discriminator. It stops short of differentiating itself from buy_crypto_price or buy_coin_* style siblings, which is the only gap.

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 context is implied rather than stated: the tool is for fetching NIGHT spot price data. The payment terms ('$0.05 USDC on Base or Solana', 'Failed calls not charged') function as practical adoption guidance. However, there is no explicit when-to-use versus alternatives guidance (e.g. broad price tools like buy_crypto_price), so the agent must infer selection.

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