Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

search_contacts

Retrieve contacts from Freshdesk by entering a search query to locate specific customer details for support operations.

Instructions

Search for contacts in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • The main handler function for the 'search_contacts' MCP tool. It performs an autocomplete search on Freshdesk contacts API using the provided query term. Registered via the @mcp.tool() decorator.
    @mcp.tool()
    async def search_contacts(query: str)-> list[Dict[str, Any]]:
        """Search for contacts in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/contacts/autocomplete"
        headers = {
            "Authorization": f"Basic {base64.b64encode(f'{FRESHDESK_API_KEY}:X'.encode()).decode()}"
        }
        params = {"term": query}
        async with httpx.AsyncClient() as client:
            response = await client.get(url, headers=headers, params=params)
            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 only states the action 'search' without detailing what the search returns, any limitations, authentication needs, rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior.

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

Conciseness4/5

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

The description is a single, straightforward sentence with no wasted words, making it appropriately concise. However, it lacks front-loading of critical details like parameter guidance, which slightly reduces its effectiveness despite the brevity.

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 search tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't cover parameter semantics, return values, or behavioral traits, making it inadequate for the agent to use the tool effectively.

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?

The schema description coverage is 0%, and the description does not mention the 'query' parameter at all. It fails to explain what the query should contain, its format, or examples, leaving the single required parameter undocumented and unclear in usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'search' and resource 'contacts in Freshdesk', which provides a basic purpose. However, it doesn't differentiate from sibling tools like 'list_contacts' or 'get_contact', making it vague about what makes this search distinct from those alternatives.

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 such as 'list_contacts' or 'get_contact'. The description lacks any context about use cases, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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