Lists a snapshot of all currently active eNSP Telnet sessions, so AI assistants can see which lab devices are connected before sending commands or diagnosing faults.
列出当前所有活跃会话的快照。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing but never states there are no side effects, whether it requires an existing connection, or how the snapshot relates to live session state. 'Snapshot' hints at a point-in-time capture but nothing more is disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence with no filler and the core action front-loaded. It is efficient, though it is so terse that it leaves obvious questions unanswered rather than being optimally informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A zero-parameter listing tool with an output schema is a simple case, and the description tells the agent enough to invoke it correctly. However, it omits any framing of what a session is, when to call this, or how it relates to the many sibling session/device tools, leaving real gaps for an agent choosing among them.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, and an empty argument object means there is nothing for the description to disambiguate; the schema coverage is 100%. Baseline 4 applies for a no-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource (list active sessions) plus a scope qualifier (snapshot of all currently active). An agent can distinguish it from the mutating siblings ensp_close_all_sessions and ensp_cleanup_idle_sessions by its read-only listing nature. It does not, however, explicitly name an alternative or clarify what counts as an 'active session' versus a connected device.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites, and no mention of related siblings such as ensp_connect_device or ensp_close_all_sessions. Usage is only weakly implied by the verb 'list'. An agent must guess whether this is a discovery step before connecting or a monitoring step after.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.