instabox-mcp

Create an SSH token

instabox_create_ssh_token

Creates a ready-to-run SSH command with an expiring access token for a specified machine, allowing login without key management or CLI setup.

Instructions

Create a ready-to-run ssh command for a machine (no key or CLI needed). SECURITY: the token is a secret; anyone holding it can log in to the machine until it expires or is revoked, and it is shown only in this response. Prefer a short ttl. Not idempotent: each call makes another token.

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": {
      "id": "<id>"
    },
    "name": "instabox_create_ssh_token"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Machine ID (m_...) or its unique name
`name`	No	Label to recognise the token by
`ttlSeconds`	No	Lifetime in seconds (default 7 days, max 30 days)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial context beyond annotations: the token is a secret, anyone holding it can log in until expiry or revocation, it is shown only in this response, and each call creates a new token. This is exactly the security and non-idempotence information an agent needs before invoking the 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?

The description is tightly structured: purpose first, then security warning, then TTL guidance, then idempotence. Every sentence contributes actionable information.

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

Completeness5/5

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

For a secret-creating tool with no output schema, the description explains what is returned (a ready-to-run SSH command/token), that it is shown only once, and the security consequences. This is sufficient for an agent to invoke it responsibly.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents `id`, `name`, and `ttlSeconds` well. The description still adds meaningful parameter guidance by advising a short TTL because the token is sensitive, which goes beyond the schema's default/max bounds.

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 states a specific verb and resource: create an SSH token that yields a ready-to-run `ssh` command for a machine. It also clarifies that no key or CLI is needed, making the tool's purpose distinct from machine lifecycle or execution tools.

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?

The description does not explain when to choose this tool over siblings such as `instabox_exec`, `instabox_list_ssh_tokens`, or `instabox_revoke_ssh_tokens`. It gives security advice and a TTL preference, but no explicit usage context or alternatives.

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