Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

get_contact

Retrieve contact details from Freshdesk using a specific contact ID. Simplify support operations by integrating AI models to automate and manage customer interactions effectively.

Instructions

Get a contact in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_idYes

Implementation Reference

  • The main handler function for the 'get_contact' tool. It fetches a specific contact from Freshdesk API using the provided contact_id. The @mcp.tool() decorator registers this function as an MCP tool named 'get_contact'.
    @mcp.tool()
    async def get_contact(contact_id: int)-> Dict[str, Any]:
        """Get a contact in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/contacts/{contact_id}"
        headers = {
            "Authorization": f"Basic {base64.b64encode(f'{FRESHDESK_API_KEY}:X'.encode()).decode()}"
        }
        async with httpx.AsyncClient() as client:
            response = await client.get(url, headers=headers)
            return response.json()
  • The @mcp.tool() decorator on get_contact function registers it as a tool in the FastMCP server.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get a contact' which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what data is returned. For a tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence with no wasted words. It's appropriately sized for a simple tool and front-loaded with the core action, though it could benefit from more detail given the lack of other documentation.

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

Completeness2/5

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

Given the tool's complexity (simple retrieval), no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain the return values, error cases, or prerequisites, making it inadequate for an agent to use effectively without additional context.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage, and the description adds no meaning beyond the schema. It doesn't explain what 'contact_id' is (e.g., numeric ID from Freshdesk), how to obtain it, or its format. With low schema coverage, the description fails to compensate, leaving the parameter poorly documented.

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

Purpose3/5

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

The description 'Get a contact in Freshdesk' clearly states the verb ('Get') and resource ('contact'), but it's vague about what 'Get' means (retrieve details vs. fetch vs. view) and doesn't distinguish from sibling tools like 'view_contact_field' or 'list_contacts'. It's functional but lacks specificity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Sibling tools include 'list_contacts' for multiple contacts and 'search_contacts' for filtering, but the description doesn't mention these or specify that this tool is for retrieving a single contact by ID. Usage is implied but not explicit.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/effytech/freshdesk_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server