Skip to main content
Glama

Undo write-off

undo_write_off
Destructive

Reverse the most-recent write-off on a time report, restoring the written-off hours to the billable pool. The billing month must still be open. Requires Finance role or above.

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": {
      "time_report_id": "<time_report_id>"
    },
    "name": "undo_write_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
time_report_idYesID of the time report whose most-recent write-off should be reversed (required).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the danger profile is known. The description does add real value beyond them by revealing the authorization requirement (Finance role) and the state gate (open billing month), plus the fact that only the single most-recent write-off is touched, which bounds blast radius. It says nothing, however, about the preview/confirm flow or what happens on a closed month, which is the main behavioral gap left.

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-loaded with the action and its effect, then preconditions. Every clause carries information an agent needs; there is no filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, single-target mutation with no output schema, the definition covers purpose, blast radius, state precondition and authorization, which is close to complete. The one thing an agent would still want spelled out is that omitting confirm yields only a preview, a detail currently available only in the schema.

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 100% and each parameter already carries its own description, so the baseline is 3. The phrase 'most-recent write-off' does clarify that time_report_id targets the report, not a specific write-off record, which is a genuine semantic addition — but it is the only one.

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 and resource ('Reverse the most-recent write-off on a time report') plus the concrete effect ('restoring the written-off hours to the billable pool'), which makes it unmistakable against write_off_time. It stops short of explicitly naming the sibling it reverses, so sibling differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two hard preconditions up front: the billing month must still be open and the caller needs Finance role or above. What's missing is a when-not clause — e.g. behavior when no write-off exists on the report or when the month has been closed — leaving error routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources