ensp-mcp

Overview Schema Source Related Servers Score Discussions Admin

topo_connect

Connect multiple devices in a Huawei eNSP topology file with automatic port selection and interface type detection. Specify links with optional ports and line types, receiving clear errors on conflicts.

Instructions

批量连线。

Args: path: .topo 文件路径。 links: 链路列表，每项支持：

    - from / to（必填）：两端设备名。
    - fromPort / toPort：接口名（"GE0/0/1"、"GigabitEthernet0/0/1"
      都认）或接口序号。省略则自动挑该设备第一个空闲口。
    - lineType：线型，默认按接口类型自动判断（串口给 Serial，
      其余给 Copper）。也可显式写 Copper / Fiber / Serial。

举例：[{"from": "Core1", "to": "Core2", "fromPort": "GE0/0/1",
       "toPort": "GE0/0/1"},
      {"from": "Core1", "to": "PC1"}]

一个接口只能连一条线，重复占用会直接报错并指出是哪个口。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`links`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 9, 2026

TDQS

A4.7/5.0

Behavior5/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 of behavioral disclosure. It transparently states that omitted ports auto-select the first free one, line type defaults based on interface type, and duplicate interface usage raises an explicit error naming the offending port. This is exemplary behavioral transparency.

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 well-structured with bullet points and an example, front-loaded with the purpose. It is a bit lengthy but every sentence adds value, explaining defaults and error behavior. No wasted words.

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

Completeness5/5

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

The description covers all necessary aspects for an agent to call the tool correctly: parameter semantics, defaults, error handling, and a practical example. Even though an output schema exists, the input description is fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining both parameters in detail. It describes the path parameter, the structure of links with required and optional fields, accepted port formats, defaults, and provides a concrete example. This exceeds what a schema could convey.

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 performs batch connection of links in a topology file ('批量连线'), and the detailed explanation of links and their fields distinguishes it from sibling tools like topo_create, topo_layout, or topo_inspect. The purpose is specific and unambiguous.

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?

The description provides a comprehensive example and explains how optional fields behave (auto port selection, auto line type detection), making it clear when and how to use it. It doesn't explicitly mention when not to use it or alternatives, but the context of sibling tools makes the intended usage evident.

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

Install Server