Skip to main content
Glama
Sign In
Inserve-MCP

Inserve-MCP

Official
by inserveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Ticket bekijken

get_ticket
Read-onlyIdempotent

Retrieve a single ticket by ID with its categories, time registrations, and latest 20 messages. Use the ticket ID, not the reference; search first if you only have a reference.

Instructions

Get a single ticket including its categories, time registrations and the latest 20 messages (newest first). Use the ticket id, not the reference; search first when you only know the reference.

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_idYesThe ticket id (not the reference).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is to add behavioral context, which it does by disclosing the response composition and the message cap of 20 ordered newest-first. It stops short of saying what happens when a ticket does not exist or how to retrieve messages beyond the newest 20.

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 sentences, front-loaded with the return contents and then the identifier rule. Every clause carries information; nothing is redundant or padded.

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?

With no output schema, the description correctly shoulders the burden of describing what comes back, including the 20-message truncation. The remaining gap is edge-case behavior - not-found handling and whether older messages are retrievable elsewhere - which is minor for a simple single-entity read.

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 coverage is 100% for the single parameter, and the schema itself already says "The ticket id (not the reference)." The description restates that plus bounds of 1 and the integer type are schema-only, so it adds workflow context but little new meaning about the parameter itself. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get a single ticket" states a specific verb and resource, and the description immediately enumerates what is bundled in the response (categories, time registrations, latest 20 messages). The word "single" plus the pointer to searching first distinguishes it cleanly from the sibling search_tickets.

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

Usage Guidelines5/5

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

It gives an explicit usage rule - use the ticket id, not the reference - and a concrete fallback condition: when only the reference is known, search first. That is exactly the when-to-use-this-vs-alternative signal an agent needs to avoid a failed call.

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