NexTool MCP for GLPI

Get my entities

glpi_get_my_entities

Read-onlyIdempotent

Retrieve GLPI entities available to the current user to see which organizations and sub-entities they can access, scoping tickets, assets, and ITIL data.

Instructions

Get the list of entities available to the current user.

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

Input Schema

Name	Required	Description	Default
`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)

Output 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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only the useful scoping fact that results are limited to the current user's entities; it says nothing about ordering, pagination, or result size for a list operation.

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?

One front-loaded sentence with the scope constraint stated immediately and zero filler. Nothing to trim.

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 no explanation, and the operation is a simple read with no required parameters. The only real omission is routing guidance against the several entity-related siblings.

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 both parameters (fields, format) have documented enums, so the schema fully carries parameter meaning. The description adds nothing about these options, which is acceptable but not additive.

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?

Specific verb ('Get the list') plus resource ('entities') and a clear scope qualifier ('available to the current user'). This implicitly separates it from glpi_list_entities (all entities) and glpi_get_entity (single entity), but it never names those siblings, so the differentiation is inferred rather than explicit.

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 guidance and no mention of alternatives such as glpi_list_entities, glpi_get_entity, or glpi_get_my_profiles, even though the description's 'my' scope exists precisely to contrast with the broader list. Usage can only be inferred from the name and scope phrase.

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

Deploy Server