instabox-mcp

Inspect a machine's Secrets

instabox_get_machine_secrets

Read-onlyIdempotent

Retrieve a machine's selected organization secrets plus outbound proxy and guest environment delivery status using its ID or name; returns metadata only.

Instructions

Show which org Secrets a machine has selected and the delivery status of the outbound proxy and the guest environment (metadata only).

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_get_machine_secrets"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Machine ID (m_...) or its unique name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by clarifying that the output is metadata only and that it covers delivery status for the proxy and guest environment, though it does not describe output shape or any authorization requirements.

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 a single front-loaded sentence with no redundant or wasted text. It efficiently states the core behavior and the metadata-only constraint.

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?

For a simple one-parameter read tool with complete annotations and high schema coverage, the description is mostly sufficient: it names the inspected data and the metadata-only limitation. It lacks detail about the returned status fields or output structure, but no output schema exists to compensate and the tool remains understandable.

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

Parameters3/5

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

There is only one parameter and schema description coverage is 100%, so the schema fully documents the machine id/name input. The description adds no parameter-level meaning beyond what the schema provides, making 3 the appropriate baseline.

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?

The description uses a clear verb ("Show") and names the specific resource: org Secrets selected by a machine, plus delivery status for the outbound proxy and guest environment. It is distinguishable from read siblings like get_machine, but it does not explicitly route against close siblings such as update_machine_secrets or refresh_machine_secrets.

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

Usage Guidelines3/5

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

The read-only inspection purpose is implied by "Show" and "metadata only," but there is no explicit guidance on when to use this tool versus alternatives like update_machine_secrets, refresh_machine_secrets, or list_org_secrets. The usage context is inferable rather than stated.

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