Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ports Search Field

ports_search_field
Read-onlyIdempotent

Search LibreNMS ports by a specific field such as ifAlias, ifDescr, or ifName to find matching interfaces. Control results with search term, limit, and offset for pagination.

Instructions

Search ports in LibreNMS by specific field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesField to search: ifAlias, ifDescr, ifName, ifType, etc.
limitNoMaximum number of results to return
offsetNoNumber of results to skip (offset) for pagination
searchYesSearch term

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.10.3
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum number of results to return",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of results to skip (offset) for pagination",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.9.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds the operation type and resource scope, but no deeper behavioral details such as matching behavior, pagination nuances, or result shape. No contradiction with annotations exists.

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?

The description is one concise, front-loaded sentence that avoids filler and immediately communicates the core operation. It could be slightly more informative, but it is appropriately sized for a simple read-only search tool.

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?

Given the presence of a full output schema, complete parameter documentation, and safety-rich annotations, the description is sufficiently complete for a simple search operation. The only notable gap is the lack of explicit sibling differentiation, which is already covered in the usage dimension.

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?

The input schema has 100% description coverage for all four parameters, including field examples, limit, offset, and search term. The description does not add parameter-level meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the action ('Search'), the resource ('ports in LibreNMS'), and the mechanism ('by specific field'). This is enough to distinguish it from broader siblings like ports_search and ports_search_mac, though it does not explicitly name them.

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 phrase 'by specific field' implies the tool should be used when searching for ports by a known field such as ifAlias or ifDescr. However, the description does not explicitly state when to prefer this tool over ports_search, ports_search_mac, or port_get, leaving the routing partly to inference.

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