Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_halving

Find when the next Bitcoin or Litecoin halving occurs, including blocks and days remaining, estimated date, progress, and block reward before and after.

Instructions

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 Costs $0.001 USDC per call.

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
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 lists the returned fields (current and halving block, blocks/days remaining, estimated date, progress %, rewards), flags the key accuracy caveat that the date is estimated from block time rather than an exact timestamp, and discloses per-call cost. The only gap is no statement of failure behavior for unsupported symbols.

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 trigger followed by return contents, caveat, example and price — every sentence adds information and none are filler. Minor structural nit: the example value and the pricing sentence are run together awkwardly, slightly blunting scannability.

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 single-parameter read tool with no output schema, the description supplies the trigger, the full return payload, an accuracy caveat, an example value and cost. Nothing an agent needs to call this correctly is missing.

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?

Only one parameter with 0% schema coverage, so the description must compensate; it does by constraining the domain to Bitcoin or Litecoin and giving a concrete example (symbol=LTC). The default BTC is already carried by the schema, so nothing is repeated unnecessarily.

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?

Names a specific resource (next Bitcoin/Litecoin halving) and frames it as a user-intent trigger. No sibling tool covers halving data, so the scope is unambiguous and an agent can route on it immediately.

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?

The opening clause gives an explicit when-to-use condition anchored to user phrasing. It does not enumerate exclusions, but the absence of any competing halving-style sibling means there is no realistic alternative to disambiguate against.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.