NexTool MCP for GLPI

Create ticket validation

glpi_create_ticket_validation

Create a GLPI ticket approval request and assign a validator to route approvals to the correct user. Add an optional comment for context.

Instructions

Create an approval request assigning a validator (users_id_validate).

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": {
      "ticketId": "<ticketId>",
      "users_id_validate": "<users_id_validate>"
    },
    "name": "glpi_create_ticket_validation"
  }
}

Input Schema

Name	Required	Description
`ticketId`	Yes	Item ID
`users_id_validate`	Yes	Approver user ID
`comment_submission`	No	Comment for the approval request

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds the semantic effect — that it creates an approval request assigning a validator — which is useful context beyond the generic 'create', but it omits side effects such as notifications to the approver or the request's pending-state behavior.

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?

A single efficient sentence with the action and key parameter front-loaded and no filler. It is appropriately tight, though for a mutation tool it is arguably too sparse to fully earn its place.

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 and annotations cover the safety profile, so return values and reversibility need not be explained. However, for a create/mutation tool the description leaves the agent without any prerequisite context (ticket must exist, approver must be a valid user), which is a meaningful gap.

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% (ticketId, users_id_validate, comment_submission all documented in the schema), so the baseline is 3. The description names users_id_validate but adds no format, constraint, or meaning beyond what the schema already provides.

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 a specific verb (Create) and resource (approval request/ticket validation) and identifies the key actor field (users_id_validate). It implicitly distinguishes itself from the list/update/delete ticket-validation siblings via the verb, but never names or contrasts them explicitly.

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 guidance on when to use this versus alternatives. It doesn't state prerequisites (e.g., that the ticket must exist and be in a validatable state) or mention the sibling glpi_update_ticket_validation / glpi_list_ticket_validations that an agent might confuse this with.

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

Deploy Server