Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

create_solution_category

Generate solution categories in Freshdesk to organize support content efficiently. Use this tool to structure help articles and improve customer self-service experience.

Instructions

Create a solution category in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_fieldsYes

Implementation Reference

  • The handler function for the 'create_solution_category' tool. It is decorated with @mcp.tool(), which registers it as an MCP tool. The function validates that a 'name' is provided in category_fields, then sends a POST request to the Freshdesk Solutions Categories API endpoint to create the category.
    @mcp.tool()
    async def create_solution_category(category_fields: Dict[str, Any])-> Dict[str, Any]:
        """Create a solution category in Freshdesk."""
        if not category_fields.get("name"):
            return {"error": "Name is required"}
    
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/solutions/categories"
        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=category_fields)
            return response.json()
  • The @mcp.tool() decorator registers the create_solution_category 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 the full burden of behavioral disclosure. It implies a write operation ('Create') but doesn't specify permissions needed, whether it's idempotent, error handling, or what the response includes. This leaves significant gaps 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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly with zero waste.

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 of a creation tool with no annotations, 0% schema coverage, no output schema, and a nested object parameter, the description is incomplete. It lacks details on parameters, behavioral traits, and expected outcomes, making it inadequate for effective tool 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 adds no information about the single parameter 'category_fields'. It doesn't explain what fields are required, their formats, or examples, failing to compensate for the lack of schema details and leaving the parameter's meaning unclear.

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 ('solution category in Freshdesk'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'create_solution_category_folder', which creates a related but different resource, leaving room for potential confusion.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'create_solution_category_folder' for folders or 'update_solution_category' for modifications. It lacks context about prerequisites, typical use cases, or exclusions, offering minimal usage direction.

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