Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

create_solution_category_folder

Generate and organize solution category folders in Freshdesk to streamline support content management. Automates folder creation using specified category IDs and folder fields for efficient knowledge base structuring.

Instructions

Create a solution category folder in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_idYes
folder_fieldsYes

Implementation Reference

  • The handler function for the 'create_solution_category_folder' tool, decorated with @mcp.tool() for registration. It validates the folder name, constructs the Freshdesk API URL, and performs a POST request to create the folder.
    @mcp.tool()
    async def create_solution_category_folder(category_id: int, folder_fields: Dict[str, Any])-> Dict[str, Any]:
        """Create a solution category folder in Freshdesk."""
        if not folder_fields.get("name"):
            return {"error": "Name is required"}
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/solutions/categories/{category_id}/folders"
        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=folder_fields)
            return response.json()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create' which implies a write/mutation operation, but doesn't disclose behavioral traits such as required permissions, whether it's idempotent, error handling, or what happens on success/failure. For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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 zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. No extraneous information or redundancy is present, achieving optimal conciseness for its limited content.

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 creation tool with 2 parameters including a nested object), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't explain what the tool returns, error conditions, or parameter details, making it inadequate for reliable agent use. More context is needed to compensate for the lack of structured data.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'category_id' refers to (e.g., ID of an existing category) or what 'folder_fields' should contain (e.g., name, description). With 2 required parameters and no schema descriptions, the description fails to provide essential semantics, leaving parameters undocumented.

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 folder in Freshdesk'), making the purpose unambiguous. It distinguishes from siblings like 'create_solution_category' (creates categories, not folders) and 'create_solution_article' (creates articles, not folders), though it doesn't explicitly mention these distinctions. The purpose is specific but could be more precise about what a 'solution category folder' entails.

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. It doesn't mention prerequisites (e.g., needing an existing category), exclusions, or comparisons to sibling tools like 'update_solution_category_folder' or 'list_solution_folders'. The description lacks context for decision-making, leaving the agent to infer usage from the name alone.

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