NexTool MCP for GLPI

List problems

glpi_list_problems

Read-onlyIdempotent

List GLPI problem management items, most recently updated first, showing status, priority, and category names.

Instructions

List problem management items, most recently updated first by default, with status_name and priority_name (in the GLPI user's language) and category_name.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort column (default date_mod = last update)
`order`	No	Sort direction (default desc = most recent first)
`range`	No	Pagination range, e.g. 0-49
`fields`	No	Field set: 'essential' (default, trims internal GLPI fields) or 'all'
`format`	No	Output format: 'json' (default) or 'markdown' (a table for listings, key/value lines for one item; returned in both the text and the structured result)
`expand_dropdowns`	No	Expand dropdown IDs to names

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No
`note`	No	Pagination hint: how to fetch the next page
`count`	No	Items in this page
`format`	No	'markdown' when data holds the markdown rendering

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.2Oct 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world. The description adds the useful behavioral fact that output is enriched with human-readable name fields in the user's language. It doesn't mention pagination limits, result caps, or auth requirements, so it's adequate but not rich.

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?

Single sentence, front-loaded with the verb+resource, then default ordering and enriched fields. Efficient and low noise; minor weakness is the comma-heavy clause stack that slightly buries the field-enrichment fact.

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

Completeness4/5

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

For a read-only list tool with a rich input schema (6 documented params, enums) and an output schema, the description covers purpose, default ordering, and output enrichment. Missing only exclusions/alternatives routing, which is a minor gap given the surrounding sibling set.

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 parameters are fully documented in structured data. The description only echoes the default sort behavior ('most recently updated first') already stated in the sort/order schema descriptions, adding no new semantics. Baseline 3 applies.

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 states a specific verb and resource ('List problem management items') and differentiates from siblings by naming the enriched output fields (status_name, priority_name, category_name) and the default ordering. An agent can tell this apart from glpi_get_problem (single item) and glpi_search (generic search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage as a listing tool with default sort/order, but stops short of explicit routing to alternatives like glpi_get_problem for a single problem or glpi_search_problem_followups. The default-sort cue helps orient intent but no when-to-use/when-not guidance is provided.

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

Deploy Server