ENSP-MCP AI

Overview Schema Source Related Servers Discussions Admin

Get Topology Context

get_topology_context

Read the topology uploaded from the web UI to help the AI identify current devices, links, and local ports before topology-aware tasks.

Instructions

Preferred first step for topology-aware tasks. Read the latest topology uploaded from the web UI so the AI can understand current devices, links, and local ports.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 21, 2026

TDQS

A3.9/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, and it does add real value by disclosing data provenance: the topology only reflects what was uploaded via the web UI, implying possible staleness. It does not state what happens when no topology exists, whether any permissions are required, or the shape/volume of the returned graph.

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?

Two sentences with no waste, and the workflow positioning ('preferred first step') is front-loaded ahead of the data description.

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 zero-argument read tool with no output schema, the description conveys the data source and the three entity types returned, which is close to sufficient. It leaves open the stale/empty-topology case, which an agent operating a topology workflow would benefit from knowing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing argument semantics that do not exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Read the latest topology') and names the payload it yields (devices, links, local ports), which separates it from discovery siblings. It stops short of naming discover_topology or find_topo_files explicitly, so an agent must still infer the boundary from 'latest topology uploaded from the web UI'.

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?

'Preferred first step for topology-aware tasks' gives a clear trigger condition and positions the tool at the start of a workflow. It offers no explicit when-not guidance or named alternative (e.g., discover_topology, sync_topology_devices) for the case where no topology has been uploaded yet.

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