Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Get SSH Access

ssh_access

Issue a one-time SSH login command and temporary password for a pod, expiring in minutes, so users can connect only when they request it.

Instructions

Get a one-time SSH login for a pod, only when the user asks to connect: the command to run and a password that expires in a few minutes (expires_at). It needs a read & write key; each call issues a new password. Give both to the user and nothing else — never run the command yourself or put the password in files, commits or other tools. The server keeps no operation record of this call, so operation_status can't look it up and a repeated call runs again.

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": {
      "pod": "<pod>"
    },
    "name": "ssh_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYes
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: the password is one-time and expires in minutes (expires_at), a read & write key is required, each call mints a fresh password, and repeating the call actually re-executes. It also discloses that the server keeps no operation record, which explains the non-idempotent behavior flagged by idempotentHint=false rather than merely restating it.

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?

Front-loads the purpose and the trigger condition, then layers credentials behavior and safety constraints in short clauses. The parenthetical field list and the multi-clause safety sentence are slightly dense but every clause carries operational information.

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?

An output schema exists, yet the description still helpfully names the returned fields and their semantics (expiry), and it covers credential handling, key requirements, and non-idempotency for a security-sensitive call. The remaining hole is the undocumented pod/workspace inputs, which matter for a tool that mints live credentials.

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 0% and the description never explains the two inputs, `pod` or `workspace` — not even that workspace is optional with a null default, or how workspace selection affects which pod is reached. The detail it does give describes outputs (command/password/expires_at), not parameters, so it fails to compensate for the coverage gap.

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 and resource ('Get a one-time SSH login for a pod') and scopes it with the triggering condition 'only when the user asks to connect'. It also names the artifacts returned (command, password, expires_at), so an agent can tell this apart from key-management siblings like create_access_key or connect_storage.

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?

Gives an explicit trigger condition ('only when the user asks to connect') and explicit negative guidance ('never run the command yourself or put the password in files, commits or other tools'). It also rules out a lookup path by noting operation_status cannot resolve this call, but it never names a positive alternative tool for non-SSH access needs.

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