termix_docker_establish_ssh_session_dockerEstablishes an SSH session to a remote host, enabling Docker container management. Gives LLM agents secure access to run Docker commands on a Termix-managed server.
Establish SSH session for Docker. Establishes an SSH session to a host for Docker operations.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a state-changing operation. The description adds no behavioral detail beyond that, such as whether the session persists, requires authentication/credentials, or needs to be explicitly disconnected.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, but the second sentence is a near-identical restatement of the first, adding only the phrase 'to a host.' This redundancy wastes the small amount of space available and does not earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For an open-world, state-changing tool with an opaque body parameter and no output schema, one line of description is severely inadequate. The agent is left without input semantics, prerequisites, postconditions, or any sense of what a successful result looks like.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has a single free-form 'body' object with 0% description coverage, and the description says nothing about what the body should contain. With no parameter guidance, an agent cannot determine required fields like host, credentials, or connection options.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: it establishes an SSH session to a host for Docker operations. However, it largely restates the tool name and title, and does not distinguish itself from sibling session lifecycle tools like check_ssh_session_status, disconnect_ssh_session, or keep_ssh_session_alive.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus alternatives, such as validate_docker_availability or check_ssh_session_status. The phrase 'for Docker operations' implies some usage context, but no prerequisites, order-of-operations, or when-not-to-use information is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.