qubic-mcp

get_tick_info

Get the current Qubic network tick number, epoch, and tick duration. Understand transaction timing with ~5-second ticks and ~1-week epochs.

Instructions

Get the current Qubic network tick information. Returns the current tick number, epoch, and tick duration. Qubic processes transactions in ticks (~5 seconds each) organized into epochs (~1 week each).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Jul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description must handle behavioral disclosure. It clearly indicates a read-only operation ('Get', 'Returns') and details the three output fields. It also provides useful domain context (tick duration, epoch length). It does not discuss potential errors or explicitly confirm no side effects, but the read-only nature is well conveyed.

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?

The description is three sentences: purpose, returned fields, and background context. Every sentence carries meaningful information without redundancy. It is front-loaded with the primary action and concise.

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?

With no output schema, the description explains return values (tick number, epoch, tick duration) and provides context on tick/epoch structure. For a zero-parameter, read-only tool, this is sufficient and complete, requiring no further elaboration.

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 has zero parameters, so the input schema fully covers all inputs. Baseline for 0 params is 4; the description adds no parameter information because none is required. The description's mention of return fields adds value beyond the schema.

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?

Description clearly states the tool gets current Qubic network tick information, using specific verb 'Get' and resource 'tick information'. It lists returned fields (tick number, epoch, tick duration), which distinguishes it from other network tools like get_network_status or get_version.

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?

The description provides context about ticks and epochs but does not explicitly state when to use this tool over siblings or when not to use it. Alternatives are not mentioned, so usage guidance is implied from the outlined purpose rather than explicitly stated.

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