Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

list_canned_response_folders

Retrieve all canned response folders in Freshdesk to streamline support ticket management. Enhance efficiency by accessing pre-defined templates for automated customer interactions.

Instructions

List all canned response folders in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_canned_response_folders' MCP tool. It is registered via the @mcp.tool() decorator and fetches the list of canned response folders from the Freshdesk API v2 endpoint.
    @mcp.tool()
    async def list_canned_response_folders()-> list[Dict[str, Any]]:
        """List all canned response folders in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/canned_response_folders"
        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()
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. While 'List all' implies a read-only operation, the description doesn't address important behavioral aspects like pagination, sorting, filtering capabilities, authentication requirements, rate limits, or what format the results will be returned in.

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 perfectly concise - a single sentence that directly states what the tool does without any unnecessary words. It's front-loaded with the core functionality and wastes no space on redundant information.

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 list operation with no annotations and no output schema, the description is insufficient. It doesn't explain what information will be returned about each folder, whether there are any limitations or constraints, or how results are structured. The agent would need to guess about the output format and behavioral characteristics.

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

Parameters4/5

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

With 0 parameters and 100% schema description coverage, the baseline score is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter set.

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 ('List all') and resource ('canned response folders in Freshdesk'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'list_canned_responses', which could cause confusion about scope.

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. With sibling tools like 'list_canned_responses' and 'view_canned_response' available, there's no indication of when folder-level listing is appropriate versus response-level listing or viewing individual responses.

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