MCP Request Tracker CrunchTools

Take Ticket Tool

take_ticket_tool

Takes ownership of a ticket by assigning it to a user and opening it for work in Request Tracker.

Instructions

Take ownership of a ticket and open it.

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

Input Schema

Name	Required	Description	Default
`username`	Yes	Your username
`ticket_id`	Yes	The ticket ID number

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.6.0Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / ticket_id / description
```
Added value: +"The ticket ID number"
```
- addedInput schema / properties / ticket_id / minimum
```
Added value: +1
```
- addedInput schema / properties / username / description
```
Added value: +"Your username"
```
- 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 / ticket_id / description
```
Removed value: -"The ticket ID number"
```
- removedInput schema / properties / username / description
```
Removed value: -"Your username"
```
- 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 burden of behavioral disclosure. It does not say whether the operation fails if the ticket already has an owner, whether it reassigns or errors, whether it is idempotent, whether special permissions are required, or that it is a mutation that changes status to open. For a write tool with zero annotation coverage this is a substantial gap.

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 short sentence with the action front-loaded and no filler. It is arguably too terse to be fully appropriate for an unannotated mutation tool, but as pure conciseness it is efficient and well-structured.

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 two-parameter mutating tool with no annotations and several overlapping siblings, the description omits side effects, failure conditions, permissions, and sibling routing, leaving the agent under-informed about the consequences of the call.

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 required parameters (ticket_id, username) are already documented in the schema. The description adds only the implication that username becomes the owner, which the field description ('Your username') already conveys. Baseline 3 is appropriate when the schema does the work.

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 compound action on a specific resource: taking ownership of a ticket and opening it. An agent can tell it is a self-assignment plus status-change operation. However, it never distinguishes itself from the sibling tools set_ticket_owner_tool and open_ticket_tool, which appear to do the same things separately.

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 combined tool versus calling set_ticket_owner_tool and open_ticket_tool, nor any prerequisite (e.g. ticket must be unassigned) or exclusion. Usage is only weakly implied by the word 'ownership'.

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

Deploy Server