Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

update_agent

Modify agent details in Freshdesk by specifying the agent ID and updated fields to streamline support operations and maintain accurate agent records.

Instructions

Update an agent in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_fieldsYes
agent_idYes

Implementation Reference

  • The update_agent tool implementation. This async function is decorated with @mcp.tool(), which both registers the tool named 'update_agent' (matching the function name) and provides the handler logic to update an agent in Freshdesk by sending a PUT request to the Freshdesk API with the provided agent_fields.
    @mcp.tool()
    async def update_agent(agent_id: int, agent_fields: Dict[str, Any]) -> Dict[str, Any]:
        """Update 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.put(url, headers=headers, json=agent_fields)
            return response.json()
  • The @mcp.tool() decorator registers the subsequent update_agent 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 full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't disclose any behavioral traits: it doesn't mention required permissions, whether changes are reversible, rate limits, error conditions, or what happens on success. This leaves critical gaps for safe tool invocation.

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 gets straight to the point with zero wasted words. It's appropriately sized for a basic tool description and front-loads the essential information (update operation on agent resource).

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 mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what can be updated, how to format updates, what permissions are needed, or what the tool returns. The agent lacks critical information needed to use this tool effectively and safely.

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 has 0% description coverage, so both parameters are completely undocumented in structured fields. The description adds no information about what 'agent_fields' should contain or how 'agent_id' should be obtained. While it implies these parameters exist through context, it provides no semantic details about their purpose, format, or constraints.

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 ('Update') and resource ('an agent in Freshdesk'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'create_agent' by specifying an update operation rather than creation. However, it doesn't specify what aspects of an agent can be updated, which prevents a perfect score.

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. There's no mention of prerequisites (like needing an existing agent ID), when not to use it, or how it differs from related tools like 'view_agent' or 'get_agents'. The agent must infer usage from context 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