Skip to main content
Glama
MCP Connect Starter

MCP Connect Starter

by cdtalley

get_ticket

Retrieve a single support ticket by ID, including its full comment thread, to review ticket details and conversation history.

Instructions

Get one support ticket by id, including its comment thread.

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_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes
subjectYes
assigneeNo
commentsNo
priorityYes
created_atYes
updated_atYes
descriptionYes
requester_emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read-only operation, and the note that the comment thread is bundled in is genuinely useful behavior beyond the structured fields. However, it says nothing about permissions, behavior for a nonexistent or closed ticket, or whether the thread is paginated or truncated.

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?

A single front-loaded sentence with no filler; the scope ('one ... by id') and the notable payload detail are both delivered immediately.

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?

An output schema exists, so return values need not be described, and the tool is a simple one-parameter fetch. The only meaningful gaps are id format expectations and error behavior for a missing ticket, which are minor for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — ticket_id is a bare untyped-in-practice string — so the description is the only source of parameter meaning. It adds only 'by id', leaving the accepted format (numeric, prefixed, external reference) unspecified. Given the low coverage, this does not compensate adequately.

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 ('Get one support ticket') plus a scoping detail that separates it from a bulk lister: 'one ... by id'. It also discloses the payload ('including its comment thread'), so an agent knows this is the detail fetch. It stops short of naming list_tickets as the sibling alternative, but the singular scope makes the distinction inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'by id' and 'one' signal this is the single-record retrieval path versus list_tickets. There is no explicit when-to-use/when-not statement, no mention of add_ticket_comment for writes, and no prerequisite or failure-condition guidance.

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