Skip to main content
Glama

Freshdesk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Freshdesk Search Tickets

freshdesk_search_tickets
Read-onlyIdempotent

Search tickets by query (e.g., "status:2 AND priority:3" or keyword text). Returns matching ticket ID, subject, status, and priority.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query in Freshdesk syntax (e.g., "status:2", "priority:1 AND type:'Question'")
_apiKeyYesFreshdesk API key
_domainYesFreshdesk subdomain

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoArray of matching ticket objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Array of matching ticket objects",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Ticket ID",
+            "type": "number"
+          },
+          "priority": {
+            "description": "Ticket priority level",
+            "type": "number"
+          },
+          "status": {
+            "description": "Ticket status code",
+            "type": "number"
+          },
+          "subject": {
+            "description": "Ticket subject",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "query": "status:2 AND priority:1"
+  },
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "query": "type:'Question' AND status:open"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description confirms a read-only search operation but adds no additional behavioral context (e.g., rate limits, auth details) beyond what annotations offer.

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 a single sentence with examples, no filler, and front-loaded with key information. Every part earns its place.

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?

The tool is simple, annotations and full schema exist, and return fields are stated. Missing pagination or limit information, but for a search tool this is acceptable.

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%, and description adds query syntax examples and return fields. While helpful, it largely mirrors the schema with slight added context, so baseline 3 is appropriate.

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?

The description clearly states the tool searches tickets by query and lists return fields (ID, subject, status, priority). Examples of query syntax distinguish it from sibling tools like list_tickets (no query) and get_ticket (single ticket).

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 query examples and mentions return fields, implying usage for ticket searching. However, it does not explicitly state when not to use it (e.g., for full lists use list_tickets) or provide alternative sibling names.

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

All Freshdesk toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources