Skip to main content
Glama
Sign In
veilform

veilform

by asteby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run a remote command with stored secrets

ssh_exec

Run shell commands on allowlisted SSH hosts with per-command approval, injecting secret env vars via stdin and returning redacted output.

Instructions

Runs a shell command on an allowlisted SSH host (using the provisioned key). env values may contain ${secret:name}; they are delivered through stdin as exports, never argv. Needs approval per exact command; output redacted.

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": {
      "host": "<host>",
      "command": "<command>"
    },
    "name": "ssh_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoremote env vars; values may contain ${secret:name}; delivered via stdin, not argv
hostYes
commandYes
timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses allowlisting, provisioned-key auth, secret interpolation via stdin rather than argv, per-exact-command approval, and output redaction. It still omits timeout behavior, error handling, and local/remote destructive effects.

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 dense sentences, front-loaded with the core action and followed by key security constraints. There is no wasted 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 complex, annotation-free tool, it covers the critical security and approval constraints an agent must know before calling it. Gaps remain around the optional timeout_ms parameter and the exact return/output shape beyond redaction.

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 only 25%. The description repeats the env secret-interpolation detail already in the schema, adds a little host context via 'allowlisted', but leaves command and especially timeout_ms semantics unexplained.

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?

States a specific verb and resource: runs a shell command on an allowlisted SSH host using the provisioned key. This clearly distinguishes it from the secret_* and web_* siblings.

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?

Gives operational context such as the allowlisted host and per-command approval requirement, implying when it is usable. However, it does not explicitly compare it with alternatives or state when not to use it.

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

Deploy Server

Other Tools