Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_problem

Manage Freshservice problems by creating, listing, updating, closing, deleting, or associating tickets with problems.

Instructions

Manage Freshservice problems.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete',
                'filter', 'close', 'restore', 'get_fields',
                'associate_tickets', 'dissociate_ticket', 'list_tickets'.
        problem_id: Problem ID (required for get/update/delete/close/restore
                    and ticket association actions).
        requester_id: Requester user ID (required for create).
        subject: Problem subject (required for create).
        description: HTML description (required for create).
        priority: 1=Low, 2=Medium, 3=High, 4=Urgent (required for create).
        status: 1=Open, 2=Change Requested, 3=Closed (required for create).
        impact: 1=Low, 2=Medium, 3=High (required for create).
        due_by: ISO datetime due date (required for create).
        agent_id: Assigned agent ID.
        group_id: Assigned group ID.
        department_id: Department ID.
        known_error: Mark as known error (boolean).
        category/sub_category/item_category: Problem categorization.
        assets: List of associated assets [{"display_id": N}].
        analysis_fields: Analysis fields dict (problem_cause, symptom, impact).
        custom_fields: Custom fields dict.
        ticket_ids: List of ticket IDs to associate (for 'associate_tickets').
        ticket_id: Single ticket ID (for 'dissociate_ticket').
        query: Filter query for 'filter' action
               (e.g. "priority:3 AND status:1").
        page/per_page: Pagination.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryNo
actionYes
assetsNo
due_byNo
impactNo
statusNo
subjectNo
agent_idNo
categoryNo
group_idNo
per_pageNo
priorityNo
ticket_idNo
problem_idNo
ticket_idsNo
descriptionNo
known_errorNo
requester_idNo
sub_categoryNo
custom_fieldsNo
department_idNo
item_categoryNo
analysis_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description must carry the full burden of disclosing side effects and behavioral traits. It lists actions like 'delete' and 'close' but does not explain consequences (e.g., irreversibility, status transitions, permission needs). Some parameter-level details like 'known_error: Mark as known error' add minor behavior context, but overall the description lacks critical behavioral information for a mutation-heavy tool.

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 structured as a clear Args list, front-loaded with the action enumeration. It is lengthy due to 24 parameters, but every line adds necessary information. The formatting is consistent and scannable, though it repeats 'required for create' multiple times, slightly reducing conciseness.

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

Completeness4/5

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

Given the tool's high complexity (24 parameters, many actions) and the presence of an output schema, the description is fairly complete. It specifies which parameters are required for which actions, provides value enums for priority/status/impact, and gives a filter query example. Minor gaps exist (e.g., get_fields action not explained, no detail on pagination behavior), but the essentials are covered.

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?

The input schema has zero description coverage, so the description compensates well by explaining each parameter's purpose and value mappings (e.g., priority 1=Low, 2=Medium, status values, query example, assets format, analysis_fields contents). It provides clear, actionable semantics beyond the bare schema definitions, though a few parameters like custom_fields remain generic.

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 opens with 'Manage Freshservice problems' and then enumerates a comprehensive list of actions (list, get, create, update, delete, filter, close, restore, etc.), making it clear that this tool handles a wide range of problem management operations. While 'manage' is generic, the action list provides specific resource/operation clarity and distinguishes it from sibling tools like manage_problem_note or manage_problem_task.

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?

Usage context is implied through the action list and parameter requirements (e.g., 'problem_id required for get/update/delete/close/restore'), but there is no explicit guidance on when to choose this tool over related siblings such as manage_problem_note or manage_ticket. The description does not state exclusions or alternatives, so it provides only implied usage.

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