Skip to main content
Glama

obit_extend

Extend the tracked lifespan of files by ledger ID or absolute path, resetting the expiry countdown from now when a file is already due.

Instructions

Extends tracked lifespans by ID or absolute path, counted from now when already due.

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>",
      "lifespan": "<lifespan>"
    },
    "name": "obit_extend"
  }
}

Input Schema

NameRequiredDescriptionDefault
refsYesPositive ledger IDs or absolute Windows paths
lifespanYesPositive additional lifespan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations establish a mutating, non-idempotent operation, and the description adds a useful behavioral nuance: an item that is already due gets its extension counted from now rather than from the original due date. It does not cover error behavior for invalid refs, atomicity, or what the operation returns.

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

Conciseness5/5

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

The definition is a single tight sentence with no filler. The core action is front-loaded and the conditional timing detail follows efficiently.

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 two-parameter mutation tool with full schema coverage and safety annotations, this is adequate but thin. It leaves unclear what happens with invalid references and how 'lifespan' should be formatted, which an agent may need for correct invocation.

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%, so the schema already documents refs and lifespan. The description only reiterates the reference forms and adds the due-date timing note, without explaining lifespan units or format beyond what the schema provides.

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 states a specific verb ('Extends') and resource ('tracked lifespans'), and it identifies the two reference forms accepted. It does not explicitly distinguish itself from siblings such as obit_spare or obit_resurrect, but the core action is clear.

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 guidance on when to use this tool versus alternatives, nor any exclusions. 'Counted from now when already due' describes how the extension is calculated, not when the tool should be selected.

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