Skip to main content
Glama
Sign In
NexTool MCP for GLPI

NexTool MCP for GLPI

by NexTools-Solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List ticket rules

glpi_list_rules
Read-onlyIdempotent

List all ticket business rules in GLPI with optional pagination, field selection, dropdown expansion, and JSON or Markdown output.

Instructions

List all ticket business rules (RuleTicket) with optional pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "glpi_list_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoPagination range, e.g. 0-49
fieldsNoField set: 'essential' (default, trims internal GLPI fields) or 'all'
formatNoOutput 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_dropdownsNoExpand dropdown IDs to names

Output Schema

NameRequiredDescriptionDefault
dataNo
noteNoPagination hint: how to fetch the next page
countNoItems in this page
formatNo'markdown' when data holds the markdown rendering

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, lowering the disclosure bar. The description adds that pagination is optional, which is useful, but does not mention the return shape or default behavior for the 'fields'/'format' modifiers. With safety fully covered by annotations, a 3 is appropriate.

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?

A single compact sentence that leads with the verb and resource and qualifies it with pagination. No filler or repetition of schema/annotation content.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a read-only list with 4 fully-documented optional params, the description is virtually sufficient; a note about default fields/format behavior would push it higher.

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% and each of the 4 params is fully documented there, so the schema does the heavy lifting. The description's phrase 'optional pagination' hints at the range param but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema is complete.

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?

States a specific verb (List), a specific resource (ticket business rules, RuleTicket), and the scope (all). The parenthetical 'RuleTicket' disambiguates it from the sibling criteria/action rules tools (glpi_list_rule_criteria, glpi_list_rule_actions) which manage different rule facets. An agent can distinguish it from glpi_get_rule_ticket (singular get) as well.

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 when-to-use or when-not-to guidance, and no mention of the natural alternatives (glpi_get_rule_ticket for a single rule, or sibling rule_criteria/rule_actions tools). The reader must infer the routing themselves.

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

Deploy Server

Other Tools