ssh-mcp

by m-kvn

Overview Schema Source Related Servers Discussions Admin

Python

Local

ssh_job_status

Check the status of a background SSH job and get its output, with option to show specified lines from the end.

Instructions

Check the status of a background job and retrieve its output.

Args: job_id: The job ID returned by ssh_run_background. tail_lines: Number of lines to show from the end of stdout/stderr. host: SSH host alias from config. Uses default if omitted.

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": {
      "job_id": "<job_id>"
    },
    "name": "ssh_job_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes
`tail_lines`	No
`host`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The description explains what the tool does but lacks detail on behavioral traits such as whether it blocks, poll frequency, or error handling. No annotations are provided to supplement this.

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 concise with a clear purpose sentence followed by an Args section, front-loading important information without extraneous text.

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?

Given the absence of output schema and schema descriptions, the description covers input parameters well. It could specify the output format (status and output structure) for greater completeness.

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

Parameters5/5

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

With 0% schema description coverage, the description fully explains each parameter: job_id's source, tail_lines' meaning, and host's alias usage, adding significant value beyond the schema.

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 clearly states 'Check the status of a background job and retrieve its output,' specifying the verb and resource. It distinguishes from sibling tools like ssh_run_background, which starts jobs.

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?

The description indicates that it should be used after ssh_run_background by referencing the job_id it returns. However, it does not explicitly mention when not to use it or alternative tools.

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