Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_department

Manage Freshservice departments by creating, updating, deleting, listing, and filtering department records. Retrieve department details with pagination and custom field support.

Instructions

Manage Freshservice departments.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete',
                'filter', 'get_fields'.
        department_id: Department ID (required for get/update/delete).
        name: Department name (required for create).
        description: Description text.
        head_user_id: User ID of department head.
        prime_user_id: User ID of department prime contact.
        domains: List of email domains for the department.
        custom_fields: Custom field values dict.
        query: Filter query string for 'filter' action
               (e.g. "name:'Engineering'").
        page/per_page: Pagination.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
pageNo
queryNo
actionYes
domainsNo
per_pageNo
descriptionNo
head_user_idNo
custom_fieldsNo
department_idNo
prime_user_idNo

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 burden of disclosing side effects and behavior. It only lists actions and parameters without explaining consequences of delete/update, permission requirements, rate limits, or whether changes are reversible. The read-only actions (list/get/get_fields) are not differentiated from mutating ones behaviorally.

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 front-loaded with a one-sentence purpose followed by a parameter list. It avoids unnecessary prose, but the parameter list is unstructured and could benefit from grouping or bolding. Overall efficient.

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 the tool's complexity (11 parameters, 7 actions) and no annotations, the description is minimal. It covers all parameters and actions but lacks behavioral context such as how actions differ, pagination defaults, error handling, or what get_fields returns. The output schema exists, so return values are covered, but the description doesn't guide selection between actions.

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?

Despite 0% schema coverage, the description adds meaning to every parameter: it enumerates valid action values, marks required parameters for specific actions, provides a query format example, and clarifies that domains is a list and custom_fields is a dict. This goes beyond the bare schema, though some descriptions are still terse.

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 identifies the resource (Freshservice departments) and enumerates specific actions (list, get, create, update, delete, filter, get_fields), making it clear this is a CRUD tool for departments. However, the verb 'Manage' is generic and it does not differentiate from sibling manage_* tools beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides some context by indicating which parameters are required for which actions (e.g., department_id for get/update/delete, name for create), but it does not explicitly state when to use this tool versus other manage_* tools or when to prefer 'filter' over 'list'. Usage is largely implied.

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