Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_agent_group

Create, update, retrieve, or list agent groups in Freshservice. Manage group details, assign agents, and configure auto-assignment and escalation.

Instructions

Manage agent groups.

    Args:
        action: 'create', 'update', 'get', 'list'
        group_id: Required for get, update
        name: Group name (create — MANDATORY)
        description: Group description
        agent_ids: List of agent IDs in the group
        auto_ticket_assign: Auto-assign tickets
        escalate_to: Agent ID for escalation
        unassigned_for: Duration before escalation (e.g. '30m', '1h')
        group_fields: Generic fields dict (update — alternative to explicit params)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
actionYes
group_idNo
agent_idsNo
descriptionNo
escalate_toNo
group_fieldsNo
unassigned_forNo
auto_ticket_assignNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It discloses action types and some mandatory fields but does not explain side effects, permission requirements, or interactions between parameters such as auto_ticket_assign and escalate_to/unassigned_for.

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 compact and uses a clear Args list structure. Each line provides specific parameter information without redundant filler, though it could be slightly more organized for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return values need not be described. The tool has 9 parameters and no annotations, so the description should explain action-specific constraints and field interactions; it only partially does. Overall it is adequate for a simple CRUD tool but lacks depth.

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

Parameters3/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. It lists all parameters and adds meaningful hints like 'create — MANDATORY', 'alternative to explicit params' for group_fields, and a format example for unassigned_for. However, several parameters remain only partially explained.

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 states 'Manage agent groups' and enumerates the supported actions (create/update/get/list), making the tool's purpose clear. It is distinguishable from sibling tools by the explicit 'agent group' resource, though it doesn't directly contrast with similar manage_* tools.

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 like manage_agent or manage_requester_group. It only lists the actions and required parameters, offering no context or exclusions.

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

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/forterro/freshservice_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server