Skip to main content
Glama
Sign In
SSH Remote MCP

SSH Remote MCP

by nguyenquocanhz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_task_poll

Check status, exit code, and log tail of a background SSH task. Use after ssh_exec_background to retrieve results.

Instructions

Check status, exit code, and inspect log tail of a background task launched via ssh_exec_background.

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": {
      "taskId": "<taskId>"
    },
    "name": "ssh_task_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoOptional SSH connection target. If omitted, uses default profile (homelab).
taskIdYesThe taskId returned by ssh_exec_background.
tailLinesNoNumber of log lines to tail (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. "Check" and "inspect" imply a non-destructive read, which is useful, but it does not say whether polling is safe to repeat, whether the task is consumed/cleared, or whether the call blocks – gaps that matter for a no-annotation 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?

A single front-loaded sentence with no filler; the resource comes first and the operation list follows efficiently.

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?

With no output schema, the description does enumerate what is returned (status, exit code, log tail), which is the key missing piece. It does not cover whether the task persists or is cleared after polling, a minor gap given the otherwise complete coverage.

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%, including the nested target object, taskId, and tailLines, so the schema already documents all three parameters. The description adds no format or default detail beyond what the schema provides, so baseline 3 applies.

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 set (check status, exit code, inspect log tail) against a specific resource (a background task launched via ssh_exec_background). An agent can distinguish this from ssh_exec, ssh_exec_background, and ssh_task_kill without opening any schema.

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?

Clearly ties itself to tasks launched via ssh_exec_background, which gives strong usage context. However, it never states when NOT to use it or names the alternative for stopping a task (ssh_task_kill), so routing guidance is context-rich but not complete.

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