Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

end_session

Destructive

Close a cached SSH session and verify remote completion before interrupting an active command.

Instructions

Close a cached SSH session. Verify remote completion before interrupting an active command.

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

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the destructive nature is known from structure. The description adds useful context that the session is cached and that closing may interrupt an active command, but it does not disclose what state is lost, whether the session persists remotely, or what verifying completion entails.

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?

Two short sentences, front-loaded with the action and followed by the caveat; no filler. The caveat wording 'Verify remote completion' is left undefined, which slightly undercuts an otherwise tight structure.

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

Completeness3/5

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

For a one-parameter destructive tool with annotations covering the safety profile, the minimum is present, but the undefined 'server' semantics and the vague verification step leave an agent without enough to call it confidently.

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?

The single required 'server' parameter has 0% schema description coverage and the description says nothing about it — no expected format, no indication of whether it is a name from list_servers, a hostname, or a session identifier. With one undocumented param, the description should compensate and does not.

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 and resource: 'Close a cached SSH session.' An agent can tell this terminates a session, but the 'cached' qualifier is never defined, and no distinction is drawn from the sibling disconnect_server, so an agent may hesitate between the two.

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?

The second sentence implies a when-not condition ('before interrupting an active command'), which suggests caution when a command is running. However, it never names an alternative tool (e.g., disconnect_server) or states the condition that selects this tool over it.

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