Skip to main content
Glama

obit_spare

Stop tracking specified ledger IDs or absolute paths and keep the files in place.

Instructions

Stops tracking IDs or absolute paths and leaves files in place.

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_spare"
  }
}

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.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, consistent with a mutating 'stop tracking' operation. The description adds genuinely useful behavior beyond them: files are NOT deleted. It does not say whether the ledger entry is removed outright, what happens for unknown refs, or whether the operation can be undone via obit_resurrect.

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?

One short sentence, front-loaded with the action and immediately followed by the key non-obvious guarantee ('leaves files in place'). No wasted wording, though it is arguably too terse for the ambiguous 'obit' vocabulary.

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 single-parameter, no-output-schema tool this is close to adequate, but it omits what becomes of the ledger entry itself and how the operation relates to obit_resurrect or obit_bury. An agent can call it, but cannot fully predict the resulting state.

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 description coverage is 100% for the single refs parameter, so the schema already documents 'positive ledger IDs (optionally prefixed with #) or absolute Windows paths'. The description restates that distinction but adds no new constraints such as mixed-array handling or behavior on partial failures, so the baseline of 3 applies.

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?

The description gives a concrete verb+resource: it stops tracking the given IDs or paths while leaving the underlying files untouched. That scope ('leaves files in place') implicitly separates it from omicide-style siblings like obit_bury that presumably remove files, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the right call when it wants to detach entries from the ledger but keep files on disk. There is no explicit when-to-use statement and no named alternative (e.g. use obit_bury to also delete the file, obit_graveyard to inspect).

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