GNS3 NetForge MCP

Overview Schema Source Related Servers Discussions Admin

notification

Subscribe to GNS3 server event streams and read buffered node, link, project, or log events on demand. Filter events, check status, or stop listening as needed.

Instructions

Subscribe to GNS3 server event notifications and read buffered events.

GNS3 streams real-time events: node state changes, link updates, log messages, etc. This tool subscribes to the stream in background and buffers events for on-demand reading.

Actions: - subscribe: Start listening to notification stream (controller or project-level) - read: Read buffered events (supports diff/all/last modes with optional action filter) - unsubscribe: Stop listening and clear buffer - status: Check subscription status and buffer stats

Event types (action field): Controller: compute., project., template.*, log.error, log.warning, log.info, ping Project: node.created/updated/deleted, link.created/updated/deleted, drawing.created/updated/deleted, snapshot.restored, ping

Examples: # Subscribe to all events >>> notification(action="subscribe")

# Subscribe to specific project events
>>> notification(action="subscribe", project_id="abc-123")

# Read new events since last read
>>> notification(action="read")

# Read only node events
>>> notification(action="read", filter_action="node.")

# Read only log errors
>>> notification(action="read", filter_action="log.error")

# Check status
>>> notification(action="status")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Read mode: 'diff' (new since last read, default), 'all' (entire buffer), 'last' (last N events)	diff
`limit`	No	Max events to return (default: 100)
`action`	Yes	Action: 'subscribe' (start listening), 'read' (get events), 'unsubscribe' (stop), 'status' (check subscription)
`project_id`	No	Project ID for project-level notifications. Omit for controller-level (all events).
`filter_action`	No	Filter events by action prefix (e.g., 'node.updated', 'log.error', 'link.')

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.54.2Oct 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description must fully disclose behavioral traits. It explains that the tool subscribes in the background, buffers events, and supports read modes (diff/all/last). However, it omits details like buffer capacity, behavior on duplicate subscription, or whether subscription persists across calls. This is adequate but leaves some 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 well-structured: a brief overview, a bullet list of actions, a categorized list of event types, and multiple examples. Every section earns its place, and the most critical information (core actions) is front-loaded. No redundant or vague sentences.

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 (subscribe/read/unsubscribe/status with filtering) and the presence of an output schema, the description covers all necessary context: actions, parameters, event types, examples, and project vs controller scope. It leaves no obvious gaps for an AI agent to invoke the tool correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds significant value by explaining each action's purpose, providing the list of event types (e.g., node.created, log.error), and giving concrete examples. This goes beyond the schema property 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 'Subscribe to GNS3 server event notifications and read buffered events.' It specifies the verb (subscribe/read/unsubscribe/status) and the resource (GNS3 server event notifications). The tool's function is distinct from its siblings (e.g., project, node, link), which focus on direct manipulation rather than event streaming.

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 clear context on when to use each action (subscribe, read, unsubscribe, status) with examples. It explains project-level vs controller-level subscription. However, it does not explicitly exclude scenarios or mention when not to use this tool over alternatives (e.g., fetching current state via project/node tools instead of streaming events).

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

Deploy Server