Skip to main content
Glama

link

List network links in a project or batch connect/disconnect nodes with atomic two-phase validation to prevent partial topology changes.

Instructions

Manage network connections (links)

v0.47.0: Renamed from set_network_connections to link (CRUD consolidation).

Actions: - list: List all links in a project - batch: Execute multiple connect/disconnect operations with two-phase validation

Two-phase execution for batch operations prevents partial topology changes:

  1. VALIDATE ALL operations (check nodes exist, ports free, adapters valid)

  2. EXECUTE ALL operations (only if all valid - atomic)

Connection Operations (for 'batch' action): Connect: {action: "connect", node_a, node_b, port_a, port_b, adapter_a, adapter_b} Disconnect: {action: "disconnect", link_id}

Examples: # List links >>> link(action="list", project_id="abc-123") >>> link(action="list", project_id="abc-123", format="json")

# Connect two nodes (batch)
>>> link(action="batch", connections=[{
...     "action": "connect",
...     "node_a": "Router1",
...     "node_b": "Router2",
...     "port_a": 0,
...     "port_b": 0,
...     "adapter_a": 0,
...     "adapter_b": 0
... }])

# Disconnect link (batch)
>>> link(action="batch", connections=[{"action": "disconnect", "link_id": "abc123"}])

Returns: JSON with OperationResult (completed and failed operations) or list of links

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction: 'list' (list links) or 'batch' (batch operations)
formatNoOutput format: 'table' (default) or 'json' (for 'list')table
project_idNoProject ID (required for 'list')
connectionsNoList of connection operations (required for 'batch')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It details the two-phase validation and atomic execution, the structure of connection operations, and return types. It does not mention potential side effects or permissions.

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-organized with sections (Actions, Connection Operations, Examples, Returns) but is somewhat verbose, including historical rename info. Most content is earned, but could be slightly more concise.

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?

Given the tool's complexity (two actions, batch with validation) and high schema coverage plus output schema, the description covers all necessary aspects: actions, parameters, behavior (atomicity), examples, and return values.

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

Parameters4/5

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

Although schema coverage is 100%, the description adds significant value by showing exact JSON structures for connection operations (e.g., node_a, port_a) and providing examples that clarify parameter usage beyond the schema-defined descriptions.

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 manages network connections (links) and distinguishes it from siblings by focusing solely on link operations. The historical rename context adds clarity.

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 explains the two actions (list and batch) and their use cases, including the atomic two-phase execution for batch. However, it does not explicitly compare to sibling tools like gns3_connection or provide when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChistokhinSV/gns3-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server