NexTool MCP for GLPI

Create webhook

glpi_create_webhook

Create a GLPI webhook to trigger HTTP calls when tickets or other ITIL items are created, updated, or deleted.

Instructions

Create a webhook. Common fields: name, url, itemtype (e.g. Ticket), event (new, update, delete), is_active, payload, http_method, use_cra_challenge.

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": {
      "input": "<input>"
    },
    "name": "glpi_create_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Webhook fields

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.1/5.0

Behavior2/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, so the safety profile is covered structurally. The description adds no behavioral context beyond a field list: no mention of required permissions, that duplicate webhooks are possible (non-idempotent), or whether the webhook is immediately armed after creation.

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 sentences, front-loaded with the action and then the field inventory. Not padded, though the field enumeration is a bare list rather than prioritized into required vs optional.

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 the field list gives reasonable coverage. However, with a fully open nested input object the description does not say whether any of these fields are required or what a minimal valid payload looks like, leaving a gap for a create mutation.

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 schema's only property is an untyped free-form 'input' object, so the description is the sole source of field-level meaning. Naming name, url, itemtype, event, payload, http_method and use_cra_challenge, plus examples for itemtype (Ticket) and event (new/update/delete), materially compensates for the empty nested schema.

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?

States a specific verb and resource ('Create a webhook'), which is unambiguous against siblings like glpi_update_webhook, glpi_delete_webhook, and glpi_set_webhook_active. It does not explicitly differentiate itself from those siblings, but the create verb makes the distinction inferable without opening a schema.

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 or when-not-to-use guidance. Given five sibling webhook tools (update, delete, set_active, list, get), a sentence such as 'use glpi_update_webhook to modify an existing webhook' would be expected and is absent.

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

Deploy Server