mcp-daktela

Overview Schema Source Related Servers Discussions Admin

get_ticket

Retrieve complete details for a specific ticket using its ID. Handles both numeric IDs and prefixed formats like TK00787979.

Instructions

Get full details of a single ticket by its ID. Use this when you already know the ticket ID.

Args: name: The ticket ID (numeric, e.g. 787979). If passed with a prefix like TK00787979, the prefix is stripped automatically.

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses the prefix-stripping behavior for the ticket ID. However, it does not mention error handling, permission requirements, or confirm it is read-only. For a simple read tool this is acceptable but not comprehensive.

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?

The description is extremely concise: two sentences plus an Args block. It opens with the core purpose in the first sentence and front-loads the primary usage instruction. No redundant information is present.

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

Completeness5/5

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

For a single-parameter read tool with an output schema, the description provides enough context: it explains what the tool does, when to use it, and fully defines the parameter. The only minor gap is the lack of distinction from get_ticket_detail, but for the tool's simplicity, the description is complete.

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

Parameters5/5

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

The schema description coverage is 0%, but the description fully compensates. It explains that the 'name' parameter is a numeric ticket ID, provides an example (787979), and details automatic prefix stripping. This goes well beyond the bare schema, which only says 'string'.

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 clearly states the tool's function: 'Get full details of a single ticket by its ID.' It specifies a single ticket and the lookup by ID, distinguishing it from list-oriented tools. However, the presence of a sibling named get_ticket_detail, which likely performs a very similar function, is not addressed, and the description does not differentiate from it.

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?

The description provides clear usage context: 'Use this when you already know the ticket ID.' This tells the agent when to invoke the tool, but it does not mention when not to use it or mention alternative tools like list_tickets or get_ticket_detail.

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