Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Whether a chain is serving current state

singularityagent__chain_liveness
Read-only

Check that a chain is actually producing blocks, rather than merely answering. A chain that has halted still responds to every request, with the correct chain id, serving the last block it ever made — so a balance read from it is historical state carrying no indication that it is historical. Each configured endpoint is probed separately, so this also reports endpoints that answer but lag behind the others, and chains left with no working failover. Call it when a read looks implausible, when an answer must be current to be worth acting on, or before treating an absence as fact. status is one of: live; stale (the head is old enough that nothing here is current); lagging (endpoints disagree enough that which one answers changes the result); single (only one endpoint answered, so the next failure is total); undatable (answering, but nothing will say when the head was produced); skewed (the head is dated in the future, so its age proves nothing); down. Only live means the chain can be read with confidence, and stale in particular does not surface as an error anywhere else.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain ids or aliases to check. Defaults to every configured chain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "chain": {
+    "description": "Chain ids or aliases to check. Defaults to every configured chain.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses significant behavioral nuance: halted chains still respond with correct chain ids, endpoints are probed separately, and stale does not surface as an error elsewhere. It also defines all status values including edge cases like `undatable` and `skewed`, giving the agent a realistic model of what the tool reports. This goes well beyond what annotations alone convey.

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 long but every sentence earns its place, covering the core failure mode, per-endpoint behavior, invocation guidance, and the full status vocabulary. The key point is front-loaded: a halted chain still answers. The detailed status list is necessary because there is no output schema to define these values elsewhere.

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 fully covers the return semantics by defining every status value and explaining what `live` means for confidence. It also communicates the default behavior of checking all configured endpoints and the optional input. The tool is complex, and the description provides enough context for correct invocation and interpretation.

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?

The only parameter, `chain`, is already fully described in the schema as 'Chain ids or aliases to check. Defaults to every configured chain.' The description reinforces the idea of configured endpoints but adds no new parameter-level meaning. With 100% schema description coverage, the baseline of 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Check that a chain is actually producing blocks, rather than merely answering.' It clearly differentiates liveness checking from ordinary data reads and explains the subtle failure mode where a halted chain still serves correct-looking historical state. The title and description together make it unmistakable what this tool does.

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 description explicitly states when to call the tool: 'when a read looks implausible, when an answer must be current to be worth acting on, or before treating an absence as fact.' It does not name alternative tools or exclude specific scenarios, but the context is clear enough for an agent to decide. No misleading guidance is present.

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

All Rokha toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources