Skip to main content
Glama

Freshdesk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Freshdesk Get Contact

freshdesk_get_contact
Read-onlyIdempotent

Get full contact details by ID including name, email, phone, company, address, and ticket history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID
_apiKeyYesFreshdesk API key
_domainYesFreshdesk subdomain

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoContact ID
nameNoContact name
emailNoContact email address
phoneNoContact phone number
addressNoContact address
company_idNoAssociated company ID
created_atNoISO timestamp
updated_atNoISO timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "description": "Contact address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "company_id": {
+      "description": "Associated company ID",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "created_at": {
+      "description": "ISO timestamp",
+      "type": "string"
+    },
+    "email": {
+      "description": "Contact email address",
+      "type": "string"
+    },
+    "id": {
+      "description": "Contact ID",
+      "type": "number"
+    },
+    "name": {
+      "description": "Contact name",
+      "type": "string"
+    },
+    "phone": {
+      "description": "Contact phone number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "description": "ISO timestamp",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-freshdesk-api-key",
+    "_domain": "mycompany",
+    "id": 5678
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety behavior. It adds value by specifying the return content (e.g., ticket history), which goes beyond the minimal info. No contradictions with annotations.

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 that efficiently conveys the tool's function and key return fields. No redundant information; every part earns its place.

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?

With an output schema present, the description's mention of specific return fields is sufficient. The tool is simple and the description covers the essential aspects: what it does and what it returns. No gaps noticed.

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% with each parameter described. The description does not add additional meaning or context beyond what the schema provides (e.g., no format constraints or edge cases). 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 uses a specific verb ('Get') and resource ('full contact details by ID'), clearly stating what the tool does. It lists the fields returned (name, email, phone, company, address, ticket history), distinguishing it from sibling tools like freshdesk_list_contacts and freshdesk_get_ticket.

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?

While the purpose is clear, the description does not explicitly state when to use this tool versus alternatives (e.g., freshdesk_list_contacts for listing). The context from sibling tools implies differentiation, but no when-not-to-use guidance is provided.

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