Skip to main content
Glama

get_ticket

Read-onlyIdempotent

Retrieves a single incident ticket by ID, including its body and comments, for read-only inspection. Use ticket IDs listed in the incident resource.

Instructions

Get one ticket, with its body and comments. Read-only.

    An incident's ticket IDs are listed in its incident://<incident_id> resource.
    

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": "get_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticket_idYese.g. TKT-0001

Output Schema

NameRequiredDescriptionDefault
idYes
bodyYes
titleYes
statusYes
commentsNo
reporterYes
created_atYes
incident_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, and the description's 'Read-only' merely restates that. Beyond the annotations it does add genuine information: the response includes the ticket body and its comments, and IDs are sourced from the incident resource. It says nothing about pagination of comments, ordering, or behavior when the ticket does not exist.

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 short sentences, front-loaded with the purpose and return scope, then the one piece of setup context an agent needs. There is no filler and nothing redundant.

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 simple single-parameter read tool with full annotations, a complete input schema and an output schema, the description covers purpose, return scope and ID provenance. Only marginal gaps remain, such as not-found behavior, which are largely outside its remit given the output schema.

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?

The single ticket_id parameter is fully documented in the schema, including the TKT-#### pattern and a TKT-0001 example, so schema coverage is 100%. The description adds no additional meaning about the identifier beyond pointing to the incident resource as its source, which is baseline-appropriate.

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?

A specific verb and resource ('Get one ticket') plus the return scope ('with its body and comments'), which tells an agent this is a single-item fetch rather than a listing. It never names the sibling tools or contrasts itself with search_logs, so differentiation is implicit through the word 'one'.

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 supplies a concrete prerequisite/workflow hint: ticket IDs come from the incident://<incident_id> resource. That answers the main 'how do I know what to pass' question. It gives no explicit when-not guidance or pointer to an alternative for lookup-by-criteria, which would be needed for a 5.

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

Deploy Server

Other Tools