Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

get_ticket_conversation

Retrieve detailed ticket conversations from Freshdesk to streamline support operations and enhance ticket management. Use this tool to access specific ticket interactions for improved customer service.

Instructions

Get a ticket conversation in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYes

Implementation Reference

  • The handler function for the 'get_ticket_conversation' tool. It retrieves the conversation history for a specified ticket ID from the Freshdesk API using an authenticated GET request. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    async def get_ticket_conversation(ticket_id: int)-> list[Dict[str, Any]]:
        """Get a ticket conversation in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/tickets/{ticket_id}/conversations"
        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 registers the get_ticket_conversation function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like read-only nature, authentication needs, rate limits, error handling, or output format. It doesn't contradict annotations, but it's insufficient for a tool with zero annotation coverage.

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 front-loaded and appropriately sized for a simple tool, though this conciseness comes at the cost of detail.

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 (a read operation with 1 parameter), no annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't cover parameter semantics, behavioral context, or output expectations, leaving significant gaps for an AI agent.

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?

Schema description coverage is 0%, and the description adds no meaning beyond the schema. It doesn't explain what 'ticket_id' represents (e.g., numeric ID from Freshdesk), its format, or where to find it. With 1 undocumented parameter, the description fails to compensate for the coverage gap.

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 ticket conversation in Freshdesk' states the basic action (get) and resource (ticket conversation), but it's vague about what 'conversation' entails (e.g., comments, notes, replies) and doesn't differentiate from sibling tools like 'get_ticket' or 'update_ticket_conversation'. It avoids tautology 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 such as 'get_ticket' (which might include conversation data) or 'update_ticket_conversation'. The description implies usage for retrieving conversation details but offers no context, exclusions, or prerequisites.

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