MCP Request Tracker CrunchTools

Get My Open Tickets Tool

get_my_open_tickets_tool

Read-only

Retrieve all open tickets assigned to a user by owner username to track unresolved support requests.

Instructions

Get all open tickets assigned to a user.

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": {
      "owner": "<owner>"
    },
    "name": "get_my_open_tickets_tool"
  }
}

Input Schema

Name	Required	Description	Default
`owner`	Yes	Username to search for

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.0Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / owner / description
```
Added value: +"Username to search for"
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
Changed3 schema fields changedSep 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / owner / description
```
Removed value: -"Username to search for"
```
- addedOutput schema / description
```
Added value: +"Generic wrapper for non-object return types."
```
First observedv0.4.0Aug 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already establishes this as a safe, non-mutating read, and an output schema exists so return shape need not be described. The description adds only that results are scoped to one assignee's open tickets; it says nothing about pagination, ordering, or how 'open' is defined relative to 'new'.

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 sentence with the scope qualifier front-loaded and no filler; nothing needs to be cut. It is lean to the point of omitting useful context, but that is a completeness problem rather than a structural one.

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

Completeness3/5

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

With annotations covering safety and an output schema covering the response, the remaining burden on the description is mostly disambiguation. Given seven ticket-related siblings, the definition does not do enough to establish when this tool is the right pick over get_new_tickets_tool or search_tickets_tool, which is the one real gap an agent faces.

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% and the single parameter is documented as 'Username to search for'. The description's phrase 'assigned to a user' loosely corresponds to the owner parameter but adds no format, casing, or matching semantics beyond what the schema already states, so the baseline 3 applies.

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 states a specific verb and resource ('Get all open tickets') plus a scope qualifier ('assigned to a user'), which is enough to understand the operation at a glance. It does not, however, differentiate itself from siblings like get_new_tickets_tool or search_tickets_tool, so the agent must infer whether 'open' overlaps with 'new'.

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 explicit when-to-use guidance, no exclusions, and no mention of the obvious alternatives (search_tickets_tool for filtered queries, get_new_tickets_tool for newly created tickets). The routing decision among these closely named siblings is left entirely to inference.

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

Deploy Server