Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

view_agent

Retrieve detailed information about a Freshdesk support agent using their unique agent ID. This tool integrates with the Freshdesk MCP server to streamline agent management and support operations.

Instructions

View an agent in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes

Implementation Reference

  • The main handler function for the 'view_agent' tool. It retrieves details of a specific agent from the Freshdesk API using the provided agent_id. Decorated with @mcp.tool() for automatic registration.
    @mcp.tool()
    async def view_agent(agent_id: int)-> Dict[str, Any]:
        """View an agent in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/agents/{agent_id}"
        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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('View'), implying it's likely safe and non-destructive, but doesn't specify permissions required, rate limits, error handling, or what data is returned. This leaves significant gaps for an agent to understand how to use it effectively.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly.

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 tool's complexity (a read operation with one parameter), lack of annotations, 0% schema description coverage, and no output schema, the description is insufficient. It doesn't cover parameter meaning, behavioral traits, or return values, leaving the agent with inadequate information to invoke the tool correctly.

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 input schema has 1 parameter with 0% description coverage, and the tool description provides no information about the 'agent_id' parameter. It doesn't explain what an agent ID is, how to obtain it, or its format (e.g., integer range). The description fails to compensate for the schema's lack of details.

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 verb ('View') and resource ('an agent in Freshdesk'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_agents' or 'search_agents', which also retrieve agent information but with different scopes or methods.

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 like 'get_agents' (list all agents) or 'search_agents' (filtered search). The description lacks context on prerequisites, such as needing a specific agent ID, or exclusions for when other tools might be more appropriate.

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