Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

start_session

Read-only

Open a persistent SSH session using an existing operator-configured server alias, enabling remote Linux administration through AgenSysAdmin.

Instructions

Open a persistent SSH session using an existing operator-configured alias.

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

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds key behavioral constraints not covered by annotations, such as ensuring the session is 'persistent' and must rely on an existing 'alias.' This provides functional context to the agent beyond safety hints.

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?

It is a single, highly dense sentence that front-loads the core action and provides necessary constraints without any extraneous wording.

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 simple tool with one parameter and no output schema, the description is quite complete. It clarifies the session nature (persistent) and the prerequisite (aliased), making correct invocation highly likely.

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

Parameters5/5

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

Since schema description coverage is 0%, the description must provide context for the 'server' parameter. By specifying it must be an 'existing operator-configured alias,' it defines the exact semantic nature of the input string.

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 uses a specific verb ('Open'), clearly defines the resource (SSH session), and the specific method ('using an existing operator-configured alias'). This makes its function unambiguous.

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?

While it implies a specialized use case (only for operator-configured aliases), it does not explicitly state when to use this tool versus general connection tools like 'connect_server'. The absence of exclusions limits the score.

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