Skip to main content
Glama

Write off time

write_off_time
Destructive

Write off hours from an approved time report, removing them from the billable pool without invoicing (e.g. discounts or goodwill). 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>",
      "hours": "<hours>",
      "reason": "<reason>"
    },
    "name": "write_off_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYesNumber of hours to write off (required, must be > 0 and ≤ remaining billable hours).
reasonYesReason for the write-off (required).
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
time_report_idYesID of the approved time report to write off hours from (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

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real value beyond that with the authorization requirement and the precise accounting effect (hours leave the billable pool, no invoice created). It leaves the idempotency_key semantics to the schema despite idempotentHint=false, and does not say whether the write-off is reversible or what happens to the report's status.

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?

Two sentences, both front-loaded with the action and its consequence before the parenthetical example and the role requirement. No filler, no restatement of the title or annotations.

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 mutation with no output schema, the description covers purpose, effect, rationale, and access control, which is most of what an agent needs. The remaining gap is recoverability and post-call state (whether undo_write_off can reverse it, what the report looks like afterwards).

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 every parameter — including the confirm preview flag and idempotency_key — is already documented in structured data. The description adds contextual framing ('approved time report') but no syntax or constraint detail beyond the schema, which matches the baseline of 3.

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 names a specific verb and resource ('Write off hours from an approved time report') and states the domain effect ('removing them from the billable pool without invoicing'), which separates it from invoicing tools like mark_time_invoiced. It does not explicitly distinguish itself from the undo_write_off sibling, so an agent must infer that direction from the names.

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?

It gives a clear usage context (discounts or goodwill) and a hard prerequisite ('Requires Finance role or above'), which is exactly the kind of gating an agent needs before calling. It stops short of stating when not to use it or pointing to undo_write_off for reversal, so no explicit alternative is offered.

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