Skip to main content
Glama

obit_mktemp

Creates and registers a temporary directory with an expiry period, using an absolute working directory to target its Git project or the system temp directory outside Git.

Instructions

Creates and registers a temporary directory with a lifespan. The explicit absolute cwd selects the Git project; outside Git the system temporary directory is used.

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": {
      "cwd": "<cwd>",
      "lifespan": "<lifespan>"
    },
    "name": "obit_mktemp"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdYesAbsolute Windows working directory used to find the Git project
nameNo
sessionNo
lifespanYesPositive lifespan such as 2h or 3d

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 declare readOnlyHint=false and idempotentHint=false, so mutability is already known; the description adds useful context that a lifespan is attached and that Git detection falls back to the system temp directory. It does not say what happens when the lifespan expires, whether an existing directory is reused (relevant given idempotentHint=false), or what errors arise from a non-absolute path.

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 sentences, front-loaded with the action, and the path-selection rule follows immediately; nothing is padded. Minor cost comes from the undefined term "registers," which consumes words without resolving meaning.

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 four-parameter mutating tool with no output schema, the definition omits half the parameters and gives no sense of the return value or the effect of the lifespan. It covers the required-parameter path logic adequately but leaves the agent guessing about name, session, and post-expiry behavior.

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 50%: cwd and lifespan are documented in the schema, while name and session are undocumented in both places. The description does extend cwd semantics with the Git-project selection and temp-directory fallback, but contributes nothing about name or session, so it only partially compensates.

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 pair (creates and registers) plus a concrete resource (temporary directory) scoped by a lifespan, which separates it from mutators like obit_extend or obit_bury. However, "registers" is never defined, and the cryptic obit_ prefix carries no meaning, so the agent must infer what registration means from the sibling set.

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 statement of when to choose this tool over obit_extend or obit_list, and no prerequisites or exclusion cases. The cwd rule (Git project vs system temp fallback) is a behavioral detail rather than usage guidance, leaving selection entirely to inference.

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