Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

execute_command

Destructive

Run shell commands on remote Ubuntu/Debian servers via SSH to perform administrative tasks; disabled by default and requires local permission flags plus client approval.

Instructions

Execute arbitrary shell code. Disabled by default; requires both local permission flags and client approval.

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>",
      "command": "<command>"
    },
    "name": "execute_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes
commandYes
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

While the annotation already marks this as destructive, the description adds crucial operational behavior: the tool is disabled by default and requires specific external approvals. This informs the agent about the operational complexity and safety overhead before invoking the tool.

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?

The definition is extremely lean and efficient. Both sentences are necessary; the first defines the action, and the second defines the required preconditions for that action.

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

Completeness5/5

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

For a highly dangerous function like executing arbitrary code, the inclusion of activation status ('Disabled by default') and required permissions makes the definition highly complete from a safety and usability perspective.

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

Parameters1/5

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

The description focuses entirely on the overall operation and security posture. Since schema description coverage is 0%, it provides no semantic meaning or context for the individual parameters (server, command, timeout), failing to compensate for the lack of structured documentation.

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 strong verb ('Execute') and clearly defines the resource type ('arbitrary shell code'). It is unambiguous about the tool's primary function.

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

Usage Guidelines5/5

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

It establishes critical usage preconditions: the tool is disabled by default, and explicitly requires both 'local permission flags' and 'client approval' to function, serving as clear guardrails for the agent.

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