Skip to main content
Glama
deenesjakoruzh
effytech

Freshdesk MCP server

by effytech
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_ticket

Retrieve support ticket details from Freshdesk using a specified ticket ID to streamline customer service and enhance support operations.

Instructions

Get a ticket in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYes

Implementation Reference

  • src/freshdesk_mcp/server.py:371-382 (handler)
    The core handler function for the 'get_ticket' MCP tool. It is decorated with @mcp.tool() which serves as both the handler implementation and registration in FastMCP. Fetches ticket details from Freshdesk API using the provided ticket_id.
    @mcp.tool()
async def get_ticket(ticket_id: int):
    """Get a ticket in Freshdesk."""
    url = f"https://{FRESHDESK_DOMAIN}/api/v2/tickets/{ticket_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()

Tool Definition Quality

C2.8/5.0
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 of behavioral disclosure. It states it 'gets' a ticket, implying a read operation, but lacks details on permissions, error handling, rate limits, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 that front-loads the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, with no wasted space or redundancy.

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 complexity (a read operation with 1 parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't address parameter meaning, behavioral traits, or return values, leaving the agent with insufficient context to use the tool effectively beyond its basic intent.

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 provides no information about the 'ticket_id' parameter. It doesn't explain what a ticket ID is, its format, or where to find it, failing to compensate for the lack of schema documentation. With 1 parameter and no semantic context, this is inadequate.

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

Purpose4/5

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

The description clearly states the action ('Get') and resource ('a ticket in Freshdesk'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_tickets' (plural) by implying retrieval of a single ticket, though it doesn't explicitly contrast with other read operations like 'view_ticket_field' or 'get_ticket_conversation'.

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. With siblings like 'get_tickets', 'search_tickets', 'view_ticket_field', and 'get_ticket_conversation', the description offers no context on selection criteria, such as whether this is for single-ticket retrieval by ID versus bulk operations or related data access.

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