Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

disconnect_server

Destructive

Ends an active SSH session to a specified remote Linux server when access is no longer needed.

Instructions

Compatibility alias for end_session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "disconnect_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is disclosed structurally. The description adds nothing beyond that: it does not say what disconnecting destroys (active sessions, in-flight commands, connection state), whether it is reversible, or what the caller gets back. Since the alias target is unnamed in terms of effect, the agent learns nothing new about the behavior.

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?

A single short sentence with no padding, and the key information (alias for end_session) is front-loaded. It is tight, though the brevity comes at the cost of substance rather than being a model of efficiency.

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

Completeness2/5

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

This is a destructive, one-required-parameter tool with no output schema and zero schema description coverage, and the entire definition is one clause pointing at another tool. It leaves the agent without the effect, the parameter format, or any confirmation of return behavior. The alias reference is the only thing preventing a 1.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'server' parameter, so the description carries the burden of clarifying it — yet it says nothing about whether this is a hostname, IP, server ID, or configured server name. The bare schema title 'Server' gives only a weak hint. With an undocumented required parameter on a destructive tool, this is a clear gap.

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

Purpose3/5

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

The description identifies the tool only by reference: 'Compatibility alias for end_session.' It never states the operation (terminating a session / closing a connection) in its own words, so the agent must infer the verb+resource from the sibling. The alias framing does distinguish it from sibling tools like connect_server or start_session, which keeps it above a pure tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Compatibility alias' implies it exists for legacy callers and that end_session is the preferred entry point, but the description never says so explicitly or gives a condition selecting one over the other. The usage signal is present but only implied, which matches the 3 anchor.

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