NexTool MCP for GLPI

Create knowledge base item

glpi_create_knowbase_item

Create a GLPI knowledge base article with a name, HTML answer, and category to document solutions and share support information.

Instructions

Create a new knowledge base article. Fields: name, answer (HTML content), knowbaseitemcategories_id, etc.

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

Input Schema

Name	Required	Description	Default
`input`	Yes	Knowledge base item 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

C2.9/5.0

Behavior2/5

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

Annotations already declare the full safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false). The description adds almost nothing beyond that; the only extra behavioral signal is that 'answer' expects HTML content, and it omits permissions, duplicate behavior, or what happens if a referenced category is missing.

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 short sentences, front-loaded with the action and followed by field hints; no filler. The trailing 'etc.' is a minor weakness but the overall size is appropriate.

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?

An output schema exists so return values need no explanation, but this is a mutation whose nested input object is effectively undocumented. Listing only three fields with 'etc.' leaves an agent guessing which fields are required to create a valid article.

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 coverage is nominally 100%, but the schema's single 'input' parameter is an untyped object with additionalProperties: {}, so it documents no actual fields. The description names three fields (name, answer, knowbaseitemcategories_id) and truncates with 'etc.', adding real value but leaving required/optional status and the full field set unspecified.

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 new knowledge base article'), which cleanly separates it from the sibling list/get/update/delete knowbase tools. It doesn't explicitly name those siblings, but the create-vs-read distinction is unambiguous.

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?

No guidance on when to use this versus glpi_update_knowbase_item or glpi_create_knowbase_category, no prerequisites such as an existing category ID, and no note about duplicate prevention despite idempotentHint=false.

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

Deploy Server