sensors_listRetrieve all sensors monitored across every device in LibreNMS, with optional limit and offset for paginated results.
List all sensors across all devices.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| offset | No | Number of results to skip (offset) for pagination |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.10.3Input schema / properties / limitAdded value: +{
+ "default": 100,
+ "description": "Maximum number of results to return",
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "description": "Number of results to skip (offset) for pagination",
+ "minimum": 0,
+ "type": "integer"
+}v1.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the cross-device scoping constraint, which is useful context, but discloses no additional behavior such as pagination size limits or response ordering.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler, front-loading the action, resource, and scope. Every word contributes to meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool, the description, annotations, and fully documented parameters are sufficient. The output schema is present, so return-value detail does not need to be repeated in the description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both limit and offset are already documented in the input schema. The description adds no new parameter meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List'), resource ('sensors'), and scope ('across all devices'), clearly identifying it as a broad enumeration tool. It is readily distinguishable from sibling tools like health_sensor_get, which focus on individual sensors.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'across all devices' implies this is the right tool for unfiltered sensor enumeration, but the description gives no explicit guidance on when to prefer it over alternatives such as health_sensor_get or alerts_get. Usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.