PRO: anchor the current chain head to OpenTimestamps on demand (the chain is auto-anchored every few hours regardless).
| Name | Required | Description | Default |
|---|---|---|---|
| vigil_key | No | Legacy credential argument. Prefer the HTTP Authorization: Bearer header; omit this argument when that header authenticates the request. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of explaining behavior. It discloses that this is a proactive, likely mutating operation and that the chain is anchored automatically anyway. However, it does not mention potential costs, authentication requirements, failure modes, or what the tool returns.
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?
The description is a single concise sentence with no filler. The 'PRO:' prefix immediately signals access tier, and the core purpose plus the automatic-anchor context are front-loaded efficiently.
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 simple tool with one optional parameter, the description covers the action and the key usage context. However, the absence of an output schema and annotations means the agent is left without information about the response format, side effects, or any costs associated with this PRO feature, so the description is not fully complete.
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?
Schema description coverage is 100%, so the only parameter, vigil_key, is already fully documented in the schema. The tool description adds no additional parameter semantics, so the baseline of 3 applies.
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 states a specific verb and resource: 'anchor the current chain head to OpenTimestamps on demand.' It also distinguishes itself from the automatic anchoring process and, implicitly, from sibling tools like vigil_anchors or vigil_notarize by focusing on immediate, on-demand anchoring.
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?
The phrase 'on demand' combined with 'the chain is auto-anchored every few hours regardless' clearly indicates when an agent should call this tool: when an immediate anchor is needed instead of waiting for the periodic automatic anchor. It does not explicitly name an alternative tool, but the context is clear.
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.
The tools are organized into clear domains—receipts/notarization, leases, journals, watchdogs, and account management—and each tool has a distinct resource or action. Minor confusion is possible between vigil_anchor and vigil_anchors, or between the various verification tools, but the descriptions generally make the boundaries clear.
All tools share the vigil_ prefix and use snake_case, but the verb/noun ordering is inconsistent: vigil_get_receipt and vigil_delete_watchdog use verb-first, while vigil_journal_get and vigil_journal_delete use resource-first. Several tools are also pure nouns (vigil_chain, vigil_usage, vigil_lease_status), making the overall pattern mixed but still readable.
At 26 tools, this exceeds the 25+ threshold and feels heavy for a single MCP server, even though the tools cluster into several subsystems. Some status, info, and lease-listing tools could plausibly be consolidated without losing much capability.
The core lifecycle coverage is strong: receipts can be created, read, verified, and audited via the chain; leases have grant/renew/revoke/status/verify; journals have full CRUD; watchdogs have set/delete/status/heartbeat. Minor gaps exist, such as no direct way to update a watchdog without deleting and recreating it, but these are workable.