Skip to main content
Glama

organize_vault

Suggests where loose notes belong by matching them to similar filed notes, previewing proposed moves by default; apply=true moves a limited number with undo.

Instructions

Suggest where loose notes belong by comparing each one with its most similar filed notes. The default is a preview that changes nothing and lists moved, proposals and skipped. With apply=true the suggestion list is refreshed and no more than ENIGMA_MAX_MOVES notes are moved (0 unless the owner raises it); every move is journaled and undo_move reverses it.

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": "organize_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

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 burden and does so well: it discloses that the default mutates nothing, that apply=true refreshes the suggestion list, that moves are capped at ENIGMA_MAX_MOVES (0 by default), and that every move is journaled and reversible via undo_move. Gaps remain on who can raise the cap and what 'skipped' criteria apply.

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 sentences, front-loaded with purpose, then default mode, then the apply path. Dense but every sentence adds information; the all-caps ENIGMA_MAX_MOVES token is slightly opaque but functional.

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 one-parameter tool with no output schema, the description supplies the return shape (moved, proposals, skipped) and the safety model (default-deny cap, journaling, undo). Only the meaning of the categories and the cap's configuration are left unspecified.

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?

Schema coverage is 0% for the single boolean, so the description must define it — and it does, contrasting apply=false (preview) against apply=true (refreshed suggestions plus capped moves). That is real meaning beyond `type: boolean, default: false`, though how the ENIGMA_MAX_MOVES cap is configured is left implicit.

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 verb+resource: 'suggest where loose notes belong' by comparing against 'most similar filed notes'. That is distinct from siblings like query_notes, write_note, or consolidate_graph, and the naming of undo_move as the reversal makes the read/apply split unambiguous.

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?

Explicitly contrasts the two modes: default behavior is a no-op preview, and apply=true triggers real moves. It tells the agent which mode to pick for inspection versus mutation, though it does not name a sibling alternative for pure note search or graph consolidation.

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