Skip to main content
Glama

obit_bury

Buries absolute file paths in a restorable graveyard immediately, with Guard and identity checks so expired debug scripts, logs, or screenshots can be recovered later.

Instructions

Moves absolute paths into the restorable graveyard immediately, with the same Guard and identity checks as obit bury.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "obit_bury"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
forceNoAllows directories containing a Git repository; other Guard checks still apply
pathsYesAbsolute Windows paths to bury

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the action is reversible ('restorable graveyard'), happens 'immediately', and is gated by Guard and identity checks. It does not explain what the Guard checks verify or note that the operation is non-idempotent, which the annotations declare.

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?

A single front-loaded sentence with no filler and the key attributes (immediacy, restorability, checks) up front. The trailing clause about 'obit bury' is slightly opaque but not wasteful.

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

Completeness3/5

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

For a non-idempotent mutation with thin annotations and no output schema, the description covers reversibility and safety gating but omits failure behavior (e.g., nonexistent or non-absolute paths) and what a caller sees on success. Adequate but not complete.

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

Parameters3/5

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

Schema coverage is 67% and the description adds no parameter-level meaning; 'force' is already documented in the schema and 'note' remains unexplained in both schema and description. Baseline 3 is appropriate given partial schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb ('Moves') and a concrete resource ('absolute paths') plus the destination ('restorable graveyard'), so the outcome is unambiguous. It does not explicitly differentiate itself from siblings such as obit_mark or obit_graveyard, and the reference to 'obit bury' points at something outside the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Immediately' implies a contrast with a deferred/staged alternative, which is the only usage signal present. There is no explicit when-to-use / when-not-to-use statement and no named alternative among obit_mark, obit_spare, or obit_graveyard.

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