Skip to main content
Glama

Zendesk

by io.github.pipeworx-io

Zd Get Ticket

zd_get_ticket
Read-onlyIdempotent

Get a Zendesk ticket by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTicket ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketNoTicket details

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "ticket": {
+      "description": "Ticket details",
+      "properties": {
+        "assignee_id": {
+          "description": "Assigned user ID",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "created_at": {
+          "description": "Creation timestamp",
+          "type": "string"
+        },
+        "description": {
+          "description": "Ticket description",
+          "type": "string"
+        },
+        "id": {
+          "description": "Ticket ID",
+          "type": "number"
+        },
+        "priority": {
+          "description": "Ticket priority",
+          "type": "string"
+        },
+        "requester_id": {
+          "description": "Requester user ID",
+          "type": "number"
+        },
+        "status": {
+          "description": "Ticket status",
+          "type": "string"
+        },
+        "subject": {
+          "description": "Ticket subject",
+          "type": "string"
+        },
+        "updated_at": {
+          "description": "Last update timestamp",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 12345
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds no extra behavioral context (e.g., error handling, authentication). No contradiction.

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?

Single sentence, zero wasted words. Perfectly concise for a simple get-by-ID operation.

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 retrieval tool with a single parameter and an output schema, the description is adequate. It doesn't cover edge cases (e.g., non-existent ticket), but the output schema likely handles that.

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 covers parameter 'id' with description 'Ticket ID'. Description does not add additional meaning beyond the schema, which has 100% coverage.

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?

Description 'Get a Zendesk ticket by ID' uses a specific verb and resource, clearly distinguishing it from sibling tools like zd_list_tickets and zd_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 Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., when to use zd_search_tickets instead). Usage must be inferred from the name and schema.

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

All Zendesk toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) which all provide factual answers, making it unclear which to use. The set also mixes Zendesk tools with a large number of prediction market and data tools, creating confusion.

Naming Consistency2/5

Naming conventions are inconsistent: Zendesk tools use 'zd_' prefix, Pipeworx tools use various prefixes like 'ask_', 'bet_', 'compare_', etc., and some are named with full words. There is no uniform pattern across the set.

Tool Count2/5

35 tools is high for a server named 'Zendesk', especially since only 5 are Zendesk-specific. The majority are unrelated to Zendesk, indicating the tool count is inappropriate for the implied purpose.

Completeness1/5

For a Zendesk server, the tool set is severely incomplete, offering only basic CRUD operations (get, list, search for tickets and users). Missing essential Zendesk features like ticket creation, update, delete, or macros, while containing many irrelevant tools from other domains.

Resources