Skip to main content
Glama
Sign In
Freshdesk MCP Server

Freshdesk MCP Server

by mikeysrecipes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_ticket_field

Add a custom ticket field to Freshdesk, enabling tailored data capture on support tickets. Configure the field's properties to meet your specific requirements.

Instructions

Create a ticket field in Freshdesk.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticket_field_fields": "<ticket_field_fields>"
    },
    "name": "create_ticket_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticket_field_fieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action 'create' without explaining required permissions, side effects, or what happens to existing fields. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it is under-specified to the point of being unhelpful. Conciseness is not achieved at the expense of essential information.

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

Completeness1/5

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

Given the tool's complexity (nested object parameter, no output schema, no annotations), the description is starkly incomplete. It provides no guidance on required fields, examples, or expected behavior, making it nearly impossible for an agent to invoke correctly.

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

Parameters1/5

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

The only parameter 'ticket_field_fields' is an object, and the schema description coverage is 0%. The description adds no explanation of what fields should be included or what the object structure should be. This is a critical gap.

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 the resource ('ticket field' in Freshdesk). It is distinguishable from sibling tools like view_ticket_field or update_ticket_field because it explicitly says 'create'. However, it lacks any additional scope or context that would make the purpose more precise.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to prefer create over update, or any exclusions. The description is entirely silent on usage context.

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

Deploy Server

Other Tools