MCP Request Tracker CrunchTools

Set Time Worked Tool

set_time_worked_tool

Set the total time worked on a ticket by specifying ticket ID and minutes. Use this to track and update labor time for accurate RT reporting.

Instructions

Set the total time worked on a ticket.

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": {
      "ticket_id": "<ticket_id>",
      "minutes": "<minutes>"
    },
    "name": "set_time_worked_tool"
  }
}

Input Schema

Name	Required	Description	Default
`minutes`	Yes	Total time worked in minutes
`ticket_id`	Yes	The ticket ID number

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.6.0Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / minutes / description
```
Added value: +"Total time worked in minutes"
```
- addedInput schema / properties / minutes / minimum
```
Added value: +0
```
- addedInput schema / properties / ticket_id / description
```
Added value: +"The ticket ID number"
```
- addedInput schema / properties / ticket_id / minimum
```
Added value: +1
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
Changed4 schema fields changedSep 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / minutes / description
```
Removed value: -"Total time worked in minutes"
```
- removedInput schema / properties / ticket_id / description
```
Removed value: -"The ticket ID number"
```
- addedOutput schema / description
```
Added value: +"Generic wrapper for non-object return types."
```
First observedv0.4.0Aug 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It implies an overwrite ('set the total') but does not state whether prior time values are replaced or merged, whether any permission is required, or whether the operation is reversible — all of which matter for a mutating tool.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably too terse for a mutation tool with no annotations, which slightly undercuts 'appropriately sized'.

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

Completeness2/5

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

The presence of an output schema means return values need not be described, but the description still leaves critical gaps: no annotation coverage, no routing guidance against add_time_worked_tool, and no disclosure of overwrite semantics. For a write operation in a toolset with a very similar sibling, more context is warranted.

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 both parameters (ticket_id, minutes) are already documented with types and constraints. The description adds no additional meaning beyond what the schema provides, which is the baseline case for complete schema coverage.

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 ('Set') and resource ('total time worked on a ticket'), which is clear enough for an agent to understand the operation. However, it does not differentiate itself from the sibling add_time_worked_tool, which is the most directly competing tool — the word 'total' hints at an overwrite semantic, but the description never confirms this distinction.

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 guidance on when to use this tool versus add_time_worked_tool or update_ticket_tool. The absence of any conditional or alternative-tool routing is a notable gap given that a near-identical sibling exists in the toolset.

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

Deploy Server