Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

create_ticket_field

Add custom ticket fields in Freshdesk to organize and categorize support tickets effectively. Enables streamlined ticket management through the Freshdesk API for improved customer support operations.

Instructions

Create a ticket field in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_field_fieldsYes

Implementation Reference

  • The handler function for the 'create_ticket_field' tool. It is decorated with @mcp.tool() which registers it as an MCP tool. The function sends a POST request to Freshdesk API to create a new ticket field using the provided fields.
    @mcp.tool()
    async def create_ticket_field(ticket_field_fields: Dict[str, Any]) -> Dict[str, Any]:
        """Create a ticket field in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/admin/ticket_fields"
        headers = {
            "Authorization": f"Basic {base64.b64encode(f'{FRESHDESK_API_KEY}:X'.encode()).decode()}"
        }
        async with httpx.AsyncClient() as client:
            response = await client.post(url, headers=headers, json=ticket_field_fields)
            return response.json()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create' which implies a write operation, but doesn't mention potential side effects, permissions needed, rate limits, or what happens on failure. This is inadequate for a mutation 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, direct sentence with no wasted words, making it easy to parse. It's appropriately sized for a simple tool name, though the brevity contributes to gaps in other dimensions.

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?

For a mutation tool with no annotations, 0% schema coverage, no output schema, and a nested object parameter, the description is insufficient. It doesn't cover behavioral aspects, parameter details, or output expectations, leaving critical gaps for agent invocation.

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 single parameter 'ticket_field_fields'. It doesn't explain what fields are required, their format, or examples, failing to compensate for the lack of schema documentation.

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 ('Create') and resource ('ticket field in Freshdesk'), making the purpose immediately understandable. It distinguishes from siblings like 'create_contact_field' by specifying 'ticket field', but doesn't differentiate from 'update_ticket_field' or explain what a ticket field is, keeping it from a perfect score.

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 like 'update_ticket_field' or 'get_ticket_fields'. The description lacks context about prerequisites, such as whether this requires admin permissions or specific conditions, leaving usage unclear.

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