Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

connect_server

Read-only

Connect to a remote Linux server via SSH as a compatibility alias for starting a session; new hosts must be enrolled through the operator CLI first.

Instructions

Compatibility alias for start_session. New hosts are enrolled only through the operator CLI.

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

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the meaningful legacy/alias status and enrollment-path constraint, but leaves the critical operational question unanswered: does calling this still start a session, silently no-op, or return an error? There is mild tension between readOnlyHint=true and aliasing a session-starting sibling, though not a clear contradiction.

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 short sentences, front-loaded with the alias relationship and followed by the constraint on new enrollments. Nothing is redundant or padded.

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?

The tool is simple (one param, no output schema), so the description needs little, but it omits whether the call succeeds or errors and whether this alias is slated for removal. For a deprecated alias an agent may still call, expected outcome is the one thing that matters and is missing.

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 coverage is 0% for the single required `server` parameter, so the description carries the full burden. The enrollment sentence hints that `server` refers to an already-registered host, but it never specifies expected format (hostname, ID, alias) or what values are valid, leaving the agent to guess.

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 defines the tool only by reference ("Compatibility alias for start_session") rather than stating what invoking it actually does, so an agent must infer the effect from the sibling. It does successfully distinguish itself from the real entry point, but the verb and outcome of calling connect_server itself are left unstated.

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?

It gives a clear exclusion: "New hosts are enrolled only through the operator CLI," which tells the agent not to reach for this tool to enroll a host. Combined with the alias-to-start_session framing, the intended routing is reasonably clear, though it never explicitly says "prefer start_session instead."

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