Skip to main content
Glama

obit_mark

Registers absolute file paths with an expiry lifespan so temporary agent-written files expire on schedule; re-registering resets expiry, with Guard and identity checks applied.

Instructions

Registers absolute paths with a lifespan, as obit add does. Re-registering resets expiry. Guard and identity checks apply.

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

Input Schema

NameRequiredDescriptionDefault
atNoExpiry accepted by obit add --at; exactly one of lifespan and at is supplied
noteNo
forceNoAllows directories containing a Git repository; other Guard checks still apply
pathsYesAbsolute Windows paths to register
lifespanNoPositive lifespan such as 2h or 3d; exactly one of lifespan and at is supplied

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Beyond readOnlyHint=false and idempotentHint=false, it adds that re-registration resets expiry and that Guard and identity checks apply. Those details are useful, but the consequence of expiry and the meaning or failure behavior of those checks remain unexplained.

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?

Three short sentences front-load the primary action and then add repeat-registration and validation behavior without redundancy. The result is efficient and easy to scan, though some of its compact terminology is not self-explanatory.

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?

The schema supplies most invocation mechanics, while the description adds useful reset and validation context, making the definition minimally viable. It still leaves the practical effect of registration and expiry, the Guard and identity terminology, and sibling-selection context unclear.

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?

The schema already documents paths, lifespan, at, and force, including the exclusivity of lifespan and at. The description adds only general lifespan and reset context, and it does not compensate for the undocumented note parameter.

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?

“Registers absolute paths with a lifespan” supplies a specific action, resource, and defining attribute, while “Re-registering resets expiry” clarifies repeat behavior. It does not distinguish the tool from siblings, and “as obit add does” relies on outside knowledge.

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?

The description implies using the tool to register paths for expiry and notes that re-registering resets that expiry. It provides no explicit when-not guidance or basis for choosing this tool over another lifecycle operation.

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