MCP Request Tracker CrunchTools

Update Ticket Tool

update_ticket_tool

Modify Request Tracker ticket details—subject, priority, or queue—using the ticket ID. Specify only the fields to change; updates apply without altering omitted values.

Instructions

Update ticket fields (subject, priority, queue). All fields are optional.

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>"
    },
    "name": "update_ticket_tool"
  }
}

Input Schema

Name	Required	Description
`queue`	No	New queue name (e.g., 'General', 'Professional')
`subject`	No	New subject/title for the ticket
`priority`	No	New priority (0-99)
`ticket_id`	Yes	The ticket ID number

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.6.0Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / priority / description
```
Added value: +"New priority (0-99)"
```
- addedInput schema / properties / queue / description
```
Added value: +"New queue name (e.g., 'General', 'Professional')"
```
- addedInput schema / properties / subject / description
```
Added value: +"New subject/title for the ticket"
```
- 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."
```
Changed6 schema fields changedSep 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / priority / description
```
Removed value: -"New priority (0-99)"
```
- removedInput schema / properties / queue / description
```
Removed value: -"New queue name (e.g., 'General', 'Professional')"
```
- removedInput schema / properties / subject / description
```
Removed value: -"New subject/title for the ticket"
```
- 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?

No annotations are provided, so the description carries the full behavioral burden and falls short: it never states whether a permission/role is required, whether changes are reversible, or what an empty value does. This last point is critical because string parameters default to "" — the description leaves ambiguous whether an empty string means 'no change' or 'clear this field'.

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 short, front-loaded sentences with no filler. The only mild redundancy is 'All fields are optional,' which partially restates the schema's required list, though it does convey the partial-update intent.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with zero annotations the description is inadequate. It does not resolve the empty-string default ambiguity, name required permissions, or clarify how it relates to the many field-specific sibling mutation tools.

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 each parameter is already documented in the schema with examples and ranges. The description only restates the field names already listed in the schema, adding no syntax, format, or default-handling semantics beyond the baseline.

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 ('Update ticket fields') and names the exact editable fields (subject, priority, queue). However, it does not distinguish itself from siblings that mutate other ticket fields, such as set_ticket_status_tool, set_ticket_owner_tool, or set_time_worked_tool, so an agent must infer the boundary.

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?

The description gives no when-to-use context and no alternatives. Given a dense sibling set where other tools handle status, owner, and time-worked updates, the agent is left to guess which mutation tool to pick for a given field.

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

Deploy Server