GLPI MCP Server v2

glpi_create_ticket

Create new GLPI tickets by specifying ticket fields like name and content to log IT incidents or requests.

Instructions

Cria um novo ticket.

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_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Campos do objeto a ser criado (ex: name, content)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'creates' without mentioning permissions, input requirements beyond the schema, potential side effects, or error behavior, which is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that clearly communicates the core purpose without redundancy. It is appropriately sized and front-loaded, with every word earning its place.

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

Completeness2/5

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

Despite having only one parameter, the description lacks essential context for an agent, such as typical use cases, required fields, or interaction with sibling creation tools. The absence of output schema and annotations means the description should compensate, but it fails to do so comprehensively.

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?

The schema has 100% description coverage for the single 'input' parameter, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already states ('Campos do objeto a ser criado').

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 'Cria um novo ticket' clearly states the tool creates a new ticket, with a specific verb and resource. It distinguishes from siblings like glpi_create_problem and glpi_create_change by explicitly targeting tickets.

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?

The description provides no guidance on when to use this tool versus alternatives, such as create_problem or create_change. There are no usage exclusions, prerequisites, or references to sibling tools, leaving the agent without context for selection.

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