Skip to main content
Glama

SwapHunt crypto market context

get_halving

Read-onlyIdempotent

Use when the user asks when the next Bitcoin or Litecoin halving is. Returns current and halving block, blocks and days remaining, estimated date, progress % and block reward before and after. Estimated from block time, not an exact timestamp. Ex: symbol=LTC Free trial: 10 calls a day. More tools (30, paid per call in USDC via x402): run the local server, uvx swaphunt-mcp, https://x402.swaphunt.dev/docs

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": "get_halving"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoCoin symbol: BTC or LTCBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: the result is 'estimated from block time, not an exact timestamp' (data provenance/accuracy caveat) and a rate limit of '10 calls a day' on the free tier. These disclosures help an agent set expectations and avoid over-calling.

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

Conciseness3/5

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

The first two sentences are well front-loaded and dense with useful detail. However, the trailing marketing content ('Free trial: 10 calls a day... More tools ... run the local server ... https://x402.swaphunt.dev/docs') is promotional and dilutes the definition, costing conciseness.

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 one-parameter read-only tool with no output schema, the description fully compensates by naming the returned fields and flagging the estimate caveat. Nothing essential to correct invocation is missing, though a note on supported symbol casing or fallback behavior would complete it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `symbol` parameter is documented in-schema as 'BTC or LTC' with a default. The description restates the allowed values via 'symbol=LTC' but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair ('when the next Bitcoin or Litecoin halving is') and enumerates the returned fields (current/halving block, blocks and days remaining, estimated date, progress %, block reward before/after). It is unambiguous against siblings like get_alt_season or pm_fees, which cover unrelated domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition: 'Use when the user asks when the next Bitcoin or Litecoin halving is.' That is a clear when-to-use instruction, though it offers no when-not guidance or named alternative for adjacent questions such as historical halving data.

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.