HPE Networking Assistant

Official

Overview Schema Source Related Servers Discussions Admin

generate_topology

Generate a Mermaid diagram of the per-site network topology, mapping gateways, switches, and APs via LLDP neighbor links. Optionally include connected clients for a full view.

Instructions

Build a per-site network topology as a Mermaid diagram (plus structured nodes/edges): gateways, switches, and APs linked via switch-port LLDP neighbors. Provide a site name; set include_clients=true to add connected clients. Render the Mermaid or save it.

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

Input Schema

Name	Required	Description
`site`	No	Site name or id (optional if the org has one site).
`org_id`	No	Mist organization id (optional).
`include_clients`	No	Add connected clients as leaf nodes (optional).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.14.0Aug 8, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the output format (Mermaid plus nodes/edges), the scope (per-site), and the optional inclusion of clients. However, it does not clarify what 'save it' entails (file location, side effects) or any permissions/rate limits, leaving some behavioral ambiguity.

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?

The description is three sentences, front-loaded with the main action and output, then gives usage tips. Every sentence adds value and there is no redundancy or 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 3 optional params and no output schema, the description provides a solid overview of inputs, output, and a key flag. It lacks detailed return-value structure or error conditions, but the core usage context is adequately covered.

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 coverage is 100%, and each parameter already has a description. The description repeats the purpose of 'site' and 'include_clients' but adds no new semantic meaning beyond the schema; it does not mention 'org_id' explicitly, though the schema covers it.

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?

The description clearly states the tool builds a per-site network topology as a Mermaid diagram with structured nodes and edges, specifying the included entities (gateways, switches, APs) and the data source (LLDP neighbors). This specific verb+resource distinguishes it from all sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides direct usage guidance: 'Provide a site name' and 'set include_clients=true' for client inclusion. The context for when to use is evident, though no explicit alternatives or exclusions are mentioned relative to sibling tools.

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