Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

btc-halving

[x402 paid: $0.010 USDC on Base] BTC halving countdown: blocks left, ETA in days and estimated date. tools/call returns the live payment challenge.

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": "btc-halving"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose the material facts: the tool is paid ($0.010 USDC on Base via x402) and tools/call returns a live payment challenge rather than data. It stops short of describing error cases, whether the challenge must be paid on every call, or caching/refresh behavior, which is the remaining gap.

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?

Two compact sentences, with the payment/cost constraint front-loaded ahead of the functional description so the agent knows the cost before deciding to call. The bracketed x402 tag is slightly opaque, but it is not wasted text.

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 tool with no output schema, the description supplies what the agent needs: the return fields and the payment handshake behavior. Only the freshness/live-vs-cached nature of the countdown and post-payment failure behavior are 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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call.

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 a specific resource (BTC halving countdown) and enumerates exactly what it returns (blocks left, ETA in days, estimated date), which is more than the name alone conveys. It does not differentiate from siblings, but none of the listed siblings plausibly overlap with a halving countdown, so the risk of misselection is low.

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 implicit rather than stated: an agent can infer this is the tool to call for halving timing. There is no explicit when-to-use/when-not-to-use guidance or mention of an alternative, though the note that tools/call returns the live payment challenge does give procedural direction for actually invoking it.

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