Skip to main content
Glama
wundervault

wundervault

Official

vault_done

Signal task completion to the vault to close time-limited approvals, including admin access and any opened SSH connection. Ends approvals only; it cannot extend them.

Instructions

Call this when you have finished the task your owner gave you. It tells the vault you are done, which (by your owner's setting) ends the time-limited approvals they gave you, so nothing stays open after the work, including admin access and any SSH connection it opened. It can only end approvals, never extend them. Takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vault_done"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that approvals are terminated, names the affected privileges (admin access, SSH connections), and states the one-way constraint that it can only end approvals, never extend them. It stops short of saying what happens on a repeat call or whether termination is immediate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the trigger and then the consequences. The final 'Takes no arguments' slightly duplicates the empty input schema but costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, non-returning lifecycle tool, the description covers the trigger, the side effects and the irreversibility. Only idempotency and the state of the response are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, so the baseline is 4; the closing 'Takes no arguments' confirms the empty schema rather than adding new meaning.

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?

States a specific action ('tells the vault you are done') and its concrete effect (ending time-limited approvals), which is clearly distinct from the capability-granting siblings like vault_call, vault_sign and vault_ssh_exec.

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?

Gives an explicit trigger condition: call it 'when you have finished the task your owner gave you,' which implicitly excludes calling it mid-task. It does not spell out edge cases (e.g., calling twice or calling when nothing is open), but no alternative tool competes for this action.

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