Skip to main content
Glama

obit_resurrect

Restore expired files from the graveyard by ledger ID or absolute original path; existing files are never overwritten, and the response reports the restored path.

Instructions

Restores verified burials by ID or absolute original path. Existing files are never overwritten; the result reports the restored path.

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": {
      "refs": "<refs>"
    },
    "name": "obit_resurrect"
  }
}

Input Schema

NameRequiredDescriptionDefault
refsYesPositive ledger IDs (optionally prefixed with #) or absolute Windows paths

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations supply readOnlyHint=false and idempotentHint=false, so the bar is lower. The description contributes real context beyond them — 'Existing files are never overwritten' and 'the result reports the restored path' — but it never says what actually happens when a file already occupies the destination (skip, error, or abort) and never clarifies what 'verified' means operationally.

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?

Two tight sentences with the input form stated before the behavioral guarantee, so nothing is buried. Slightly terse given that failure behavior is left dangling.

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?

With one fully documented parameter and no output schema, little is missing structurally, and the description covers the return value ('reports the restored path'). It is still incomplete for a non-idempotent mutation: the collision case implied by 'never overwritten' and the meaning of 'verified' are exactly what an agent needs before invoking it.

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 100% and the single refs parameter is fully documented, including the '#' prefix and absolute-path format. The description's 'by ID or absolute original path' merely restates that, adding no new syntax, limits, or partial-failure semantics.

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?

Names a specific verb and resource ('Restores verified burials') and scopes the input to 'ID or absolute original path', which lets an agent immediately see it is the inverse of obit_bury. It does not, however, explicitly contrast itself with siblings like obit_extend or obit_mark, so the differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the verb that this undoes a burial and from 'verified' that unverified entries cannot be restored, but neither the prerequisite nor the failure case is spelled out.

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