Skip to main content
Glama
Sign In
HPE Networking Assistant

HPE Networking Assistant

Official
by hpe-networking-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_inventory_report

Generate a Markdown inventory of all APs and switches, including model, serial, MAC, site, status, and firmware, from your network.

Instructions

Generate a full device inventory report as Markdown (every AP and switch with model, serial, MAC, site, status, and firmware version).

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": "generate_inventory_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idNoMist organization id (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the output format (Markdown) and coverage (every AP and switch) but does not mention whether the operation is read-only, any required permissions, or the behavior when org_id is omitted (e.g., uses active org). These are material behavioral traits for a tool with no annotation support.

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?

Single sentence, grammatically clear, front-loaded with the main verb 'Generate' and immediately specifies the output format and data fields. No filler.

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?

For a tool with one optional parameter and no output schema, the description covers the purpose, output format, and included data. However, it could mention the default organization behavior and any limitations, but overall it is fairly complete.

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 schema provides a 100% description for org_id, making the parameter self-explanatory. The tool description does not add any further semantics, but the baseline of 3 is appropriate given schema coverage.

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?

Clearly states it generates a full device inventory report in Markdown, enumerating specific fields (model, serial, MAC, site, status, firmware version) for both APs and switches. This distinguishes it from sibling report tools because it covers the full inventory.

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 description implies the use case—when you need a comprehensive inventory report—but does not explicitly state when to prefer this over sibling tools like get_access_points or generate_health_report. No exclusions or alternatives are mentioned.

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