instabox-mcp

Get an operation

instabox_get_operation

Read-onlyIdempotent

Check the status of a lifecycle operation by ID, returning queued, running, succeeded, or failed states with phase and error details; optionally long-poll up to 30 seconds for changes.

Instructions

Get the status of an operation (create, start, stop, suspend, resume, delete) returned by a lifecycle call: state queued, running, succeeded or failed, plus phase and error. With waitSeconds it long-polls until the operation changes or finishes.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Operation ID (op_...)
`waitSeconds`	No	Long-poll up to this many seconds (max 30)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value beyond that by enumerating the returned states (queued, running, succeeded, failed) plus phase and error, and by disclosing that `waitSeconds` triggers long-polling that returns early on change — behavior an agent would otherwise have to guess.

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?

Two compact sentences: anaphoric core purpose first, then the long-poll modifier. No filler, no restating of the tool name as a definition.

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?

There is no output schema, so the description must carry the return shape; it does so at the level of state/phase/error but not exact field names or progress details, which is acceptable for a simple two-parameter status tool. Combined with 100% schema coverage, an agent has enough to call it correctly.

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 coverage is 100%, so baseline is 3, but the description genuinely extends the schema by explaining that `waitSeconds` polls "until the operation changes or finishes" — the early-return-on-change condition is not in the parameter description. The ID parameter's origin (a lifecycle call) is also clarified.

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 the status of an operation") and immediately scopes it by naming the operations it covers and where the ID comes from ("returned by a lifecycle call"). An agent knows exactly what this returns and can distinguish it from the machine-facing siblings without inspecting the schema.

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 clear context for when to call it — after a lifecycle call, when you need state, phase, or error — and flags the long-poll variant via `waitSeconds`. It does not explicitly say when not to use it or name a preferred alternative, but with no competing sibling for operation status the practical ambiguity is low.

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