Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_change_task

Manage tasks on a change by creating, viewing, listing, updating, or deleting them. Handle change task workflows with direct actions.

Instructions

Manage tasks on a change.

    Args:
        action: 'create', 'view', 'list', 'update', 'delete'
        change_id: The change ID
        task_id: Required for view, update, delete
        title: Task title (create)
        description: Task description (create)
        task_status: Task status int (create/update)
        task_priority: Task priority int (create/update)
        assigned_to_id: Agent ID to assign (create/update)
        task_group_id: Group ID (create/update)
        due_date: ISO date (create/update)
        task_fields: Dict of fields (update — alternative to individual params)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
actionYes
task_idNo
due_dateNo
change_idYes
descriptionNo
task_fieldsNo
task_statusNo
task_group_idNo
task_priorityNo
assigned_to_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 for behavioral disclosure. It only provides parameter usage notes and does not mention side effects, permissions, reversibility, or return behavior. For a mutation tool, this is a significant gap.

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 summary line followed by an args list, which is easy to scan. Each parameter line is concise and informative. It is slightly verbose but every line adds value.

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 complexity of 11 parameters and 5 actions, the description provides solid parameter guidance. However, it lacks behavioral context (e.g., what happens on delete) and does not explain return values, though an output schema exists. It is adequate but not fully complete.

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 description adds meaning beyond the schema by explaining which parameters are for which actions (e.g., task_id required for view/update/delete, title for create) and noting task_fields as an alternative to individual params for update. This compensates for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Manage tasks on a change' and enumerates specific actions (create, view, list, update, delete), providing a specific verb+resource combination. It distinguishes from sibling tools like manage_change or manage_change_note by focusing on tasks within a change.

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?

The action list implies when to use the tool (e.g., to create a task) but there is no explicit guidance on when to choose this over alternatives or any exclusions. The description does not mention prerequisites or alternative tools, so usage is only implied rather than clearly stated.

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