Skip to main content
Glama

krusch_reject

Idempotent

Reject a staged diff and record the reason without writing changes to disk, keeping agent edits audited and reversible.

Instructions

Reject a staged diff with a recorded reason without writing to disk.

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": {
      "task_id": "<task_id>"
    },
    "name": "krusch_reject"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

The description adds real context beyond the annotations: the reason is persisted ('recorded') while no disk write occurs, which explains why readOnlyHint=false but destructiveHint=false. It does not say where the reason is stored, what happens to the staged diff afterward, or whether the rejection can be undone, so the disclosure is partial.

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 compact sentence with the outcome and the non-disk constraint front-loaded; no filler. It is arguably too terse for a mutation tool, but nothing is wasted.

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 state-changing tool with no output schema, the definition covers the core action and safety posture but leaves the post-condition unspecified: what state the staged task ends in, whether the recorded reason is retrievable later, and what the call returns.

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 0%, so the description must carry parameter meaning. It explains the 'reason' parameter as being recorded, but says nothing about task_id, which is the required parameter and the only thing identifying which staged diff is rejected.

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?

States a specific verb (reject) applied to a specific resource (a staged diff) plus the key constraint that nothing is written to disk. An agent can distinguish this from krusch_apply_diff by the outcome alone, 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?

The phrase 'staged diff' and 'without writing to disk' imply the usage context (refusing a pending change instead of applying it), but the description never states when to choose this over krusch_abort or krusch_apply_diff, nor any prerequisite like needing an active staged task.

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