Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Arp Search

arp_search
Read-onlyIdempotent

Search LibreNMS ARP entries by IPv4 address, MAC address, or CIDR block; list all entries for a device with query 'all' and paginate results.

Instructions

Retrieve ARP entries from LibreNMS by search query.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesSearch string for ARP entries. Supports an IPv4 address, MAC address, IPv4 CIDR notation (e.g. 10.0.0.0/24), or "all" (requires the device parameter; lists all entries on that device)
deviceNoDevice hostname or ID to list entries for. Required with query "all" and only valid with it; any other combination returns an error.
offsetNoNumber of results to skip (offset) for pagination

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.12.0
    • addedInput schema / properties / device
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Device hostname or ID to list entries for. Required with query \"all\" and only valid with it; any other combination returns an error."
+}
    • changedInput schema / properties / query / description
      Previous value: -"Search string for ARP entries. Supports IP address, MAC address, CIDR notation, or \"all\" (use with device parameter for all entries on a device)"New value: +"Search string for ARP entries. Supports an IPv4 address, MAC address, IPv4 CIDR notation (e.g. 10.0.0.0/24), or \"all\" (requires the device parameter; lists all entries on that device)"
  2. 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"
+}
  3. First observedv1.9.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination behavior, result limits, or the dependency between query and device fields.

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?

A single short sentence with zero waste and the key facts front-loaded. It is efficient, though arguably too sparse for the tool's behavioral quirks.

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

Completeness3/5

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

With an output schema present and full schema description coverage, the description need not restate return values. However, for a search tool with a non-obvious query/device dependency, the description leaves everything to structured fields and offers no orienting context.

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 the query formats (IPv4, MAC, CIDR, "all") and the device coupling are fully documented in the schema. The description adds no parameter meaning beyond that, which is the baseline 3 case.

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?

States a specific verb (Retrieve) and resource (ARP entries) and identifies the source system (LibreNMS). It does not differentiate itself from nearby siblings like fdb_lookup, ports_search_mac, or device_fdb, which an agent may consider for similar lookups.

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 guidance on when to use this tool versus the many other lookup/search siblings. The only usage constraint (query "all" requires device) lives in the schema, not the description.

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