Revoke your own key. It stops authenticating immediately. Irreversible.
| 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 provided, the description carries the full burden of behavioral disclosure. It does well by stating two important consequences: authentication stops immediately and the action is irreversible. It does not mention authentication requirements or what happens to dependent artifacts, but the key behavioral traits are covered.
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 two short sentences with no filler or redundancy. Key facts are front-loaded ('Revoke your own key') followed immediately by the most important behavioral consequences.
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 one-parameter tool with no output schema, the description covers the essential information: what is revoked, how quickly it takes effect, and that it cannot be undone. It could additionally clarify the authentication requirement, but the schema's parameter description already addresses the legacy credential versus Bearer header choice.
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 one parameter is already well documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, which matches the baseline for high schema coverage.
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 action ('Revoke') and a specific resource ('your own key'), which clearly identifies what the tool does. 'Your own' disambiguates it from sibling tools like vigil_revoke_lease or vigil_delete_watchdog, so an agent can distinguish it without inspecting other schemas.
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 description clearly implies when to use the tool: when the caller needs to revoke their own API key. It does not explicitly name alternatives or state when-not-to-use, but the self-scoped wording gives enough context to avoid confusion with lease or watchdog revocation.
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.