Delete a journal slot.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| 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 provided, the description carries the full burden of behavioral disclosure. It states the destructive nature of the operation but does not mention permanence, side effects, authentication requirements, or what happens if the slug does not exist.
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 short sentence with no redundant wording. It is front-loaded and efficient, though it leans toward under-specification rather than structured completeness.
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 destructive operation with no annotations and no output schema, the description is too thin. It omits important context such as authentication via bearer header, reversibility, and result expectations, leaving an agent under-informed.
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 only 50%, with the required 'slug' parameter undocumented in the schema. The description does not clarify how the slug identifies the journal slot or whether the optional vigil_key affects behavior, so it fails to compensate for the schema gap.
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 ('Delete') and a resource ('journal slot'), which clearly states the core operation. It also differentiates from sibling tools like vigil_journal_get, vigil_journal_list, and vigil_journal_put, though the term 'slot' could be more precise.
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 guidance is given about when to use this tool versus alternatives. There is no mention of prerequisites, deletion semantics, or what distinguishes deleting a journal slot from other journal operations.
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.