Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Create Ssh Session

createSshSession
Destructive

Creates a short-lived SSH session credential for a running container, enabling temporary access to debug or manage services without long-term keys.

Instructions

Create a short-lived SSH session credential for a running container.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "createSshSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is partly covered. The description adds genuine context beyond them: the credential is short-lived and targets a running container, implying a state prerequisite and temporary authorization. However, it never explains why the operation is marked destructive, what permission level the session grants, or what the credential's lifetime or revocability actually is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the key qualifiers (short-lived, running container) come before any subordinate clause. It is efficient, though arguably too thin for a five-parameter destructive tool rather than genuinely well-proportioned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the agent gets no information about the shape of the returned credential (private key? host? user? port?), which is exactly what it needs to use the result. Combined with 20% parameter coverage and a destructive write annotation, the definition leaves material gaps for a moderately complex, nested-schema tool.

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 20% across five parameters, including a nested requestBody with a required 'component' field, and the description explains none of them. It doesn't clarify what workspaceSlug/appSlug/region/env select or what 'component' identifies (a service? a process?). With this coverage gap, the description should carry the burden and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a short-lived SSH session credential for a running container" states a specific verb (create), a specific resource (SSH session credential), and scopes it with 'short-lived' and 'running container'. It is distinguishable from the sibling getSshSession (which presumably returns an existing one), but the description never names that sibling or explicitly contrasts the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus getSshSession or execCommand, both of which appear in the sibling list and cover adjacent SSH/command work. The only implicit cue is 'for a running container', which hints at a prerequisite state but is never stated as a condition or exclusion.

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