Skip to main content
Glama
smk-h

embedded-mcp-toolkit

by smk-h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_build

Execute a build command on a remote server over SSH, wait for completion, and receive structured errors and warnings for AI analysis.

Instructions

Execute a build command on the remote server via SSH, wait for completion, classify errors/warnings, and return structured build results for AI analysis. IMPORTANT: Each session supports only ONE build at a time. For concurrent builds, open multiple sessions via ssh_shell_open and assign one build per session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory on the remote server for the build command
commandYesThe build command to execute (e.g., 'make -j8', './build.sh')
classifyNoWhether to classify output into errors/warnings/info queues (default: true)
timeoutMsNoMaximum wait time in milliseconds (default: 600000 = 10 minutes)
session_idYesThe session ID returned by ssh_shell_open or ssh_shell_login. One session supports only one build at a time — open multiple sessions for concurrent builds.
pollIntervalNoPoll interval in milliseconds to check for build completion (default: 2000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • removedInput schema / properties / maxWait
      Removed value: -{
-  "description": "Maximum wait time in milliseconds (default: 600000 = 10 minutes)",
-  "type": "number"
-}
    • addedInput schema / properties / timeoutMs
      Added value: +{
+  "description": "Maximum wait time in milliseconds (default: 600000 = 10 minutes)",
+  "type": "number"
+}
  2. First observedv0.2.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it delivers meaningful behavioral context: it waits for completion, classifies output, returns structured results, and enforces a one-build-per-session limit. It does not mention side effects like file changes on the remote server or behavior on timeout, but the disclosed behavior is substantially more than a bare mutation hint.

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 description is two sentences with no filler. The primary action is stated first, followed by the critical concurrency limitation, making the most important operational detail prominent and easy to parse.

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?

The description covers the main workflow, the blocking/waiting behavior, and the concurrency constraint, which is sufficient for correct invocation of most build tasks. It does not detail the return structure beyond 'structured build results', and there is no output schema, so an agent may have some uncertainty about the exact result format, but overall the description is reasonably complete for a moderately complex tool.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are already documented in the input schema. The tool description reinforces the session_id concurrency constraint, but it adds no new parameter-level semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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-resource pairing: execute a build command on the remote server via SSH, wait for completion, classify errors/warnings, and return structured build results. This clearly distinguishes ssh_build from generic siblings like ssh_shell_exec or serial_exec by emphasizing the build-specific workflow and structured classification output.

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?

The description explicitly states the critical usage constraint: each session supports only ONE build at a time, and for concurrent builds one must open multiple sessions via ssh_shell_open. This gives the agent concrete when-to-use and when-not-to-use guidance, plus a named alternative for the concurrent case.

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