NexTool MCP for GLPI

Add task to ticket

glpi_add_ticket_task

Add a task to a GLPI ticket with required ticket ID and content, plus optional privacy, state, duration, and technician assignment.

Instructions

Add a task to a ticket. Fields: tickets_id, content (required). Optional: is_private (0/1), state (0=Info, 1=To do, 2=Done), actiontime (seconds), users_id_tech (assigned technician).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tickets_id": "<tickets_id>",
      "content": "<content>"
    },
    "name": "glpi_add_ticket_task"
  }
}

Input Schema

Name	Required	Description
`state`	No	0=Info, 1=To do, 2=Done
`content`	Yes	Task content
`actiontime`	No	Duration in seconds
`is_private`	No	1=private, 0=public
`tickets_id`	Yes	Ticket ID
`users_id_tech`	No	Assigned technician user ID

Output Schema

Name	Required	Description	Default
`data`	No
`replayed`	No	True when an identical recent create was returned instead of repeated

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.2Oct 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already disclose the safety profile (not read-only, not destructive, not idempotent), so the description carries a lower burden, but it adds nothing behavioral beyond that — no permission requirements, no duplicate-handling, no note on how private tasks differ. The remaining text merely restates schema fields.

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?

Two front-loaded sentences with no filler: the purpose comes first, then the required/optional field breakdown. Efficient, though the field enumeration largely duplicates the schema.

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?

An output schema exists so return values need not be described, and annotations cover safety, but for a mutation tool the description omits any usage context, side effects, or prerequisites. It is minimally adequate rather than complete.

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 100%, so the schema already documents every parameter. The description repeats the field list and value meanings (state 0/1/2, actiontime in seconds) rather than adding syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 gives a precise verb+resource ('Add a task to a ticket') that cleanly separates it from siblings like glpi_add_followup, glpi_add_ticket_user, and the read counterpart glpi_list_ticket_tasks. It does not, however, explicitly name any alternative to help route the agent.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the sibling tools an agent might confuse this with (followups, solutions, ticket users). Usage can only be inferred from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server