Return Knox service health: process uptime, database latency, total anchors written, latest anchor timestamp, and the Bitcoin anchor SLA target (OpenTimestamps interval, 1-6 hour confirmation window). Mirrors the public /api/knox/health endpoint under the MCP envelope.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It lists what metrics are returned and mentions it mirrors a public endpoint, implying a read-only operation. However, it does not explicitly state that there are no side effects, no auth required, or describe rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The first sentence enumerates the return values, and the second provides the endpoint context. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter health check with no output schema, the description provides enough detail about the contents and the SLA target. It does not describe the exact output format, but that is less critical given the listed metrics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description need not compensate for schema gaps. The baseline for 0 params is 4, and the description adds context by explaining the kind of data returned.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Return') and names the resource ('Knox service health') with a detailed list of outputs. It clearly distinguishes from sibling tools like verify_anchor or anchor_file_hash, which focus on anchor operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given for when to use this tool versus alternatives. It implies a health-check use case but does not name sibling tools or state when not to use it, leaving the decision to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct: anchoring, verifying, health, descriptor, and event taxonomy. However, anchor_event and anchor_mcp_tool_call overlap in that anchor_event accepts any event type including the MCP tool call event, though the latter provides structured convenience metadata. This creates minor potential for misselection.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: anchor_*, get_*, list_*, verify_*. The verbs clearly indicate actions, and the pattern is uniform across the set.
Seven tools is well-scoped for a blockchain anchoring service. The count covers core operations, verification, health checks, and informational endpoints without bloat or redundancy.
The tool set fully covers the lifecycle: anchoring via multiple event types, verification by hash, health monitoring, descriptor access, and event taxonomy listing. Since anchoring is append-only, no update/delete operations are expected, and the surface is complete for the domain.