instabox-mcp

List templates

instabox_list_templates

Read-onlyIdempotent

Lists the machine templates available to start from, with their software and default size. Shows which templates can be created, so you pick a valid one before provisioning.

Instructions

List the templates a machine can start from (e.g. agent-browser, universal, herdr, orca) with their software and default size. Only templates with creatable: true can be used; the free plan can create from agent-browser only. Needs machines:read or images:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instabox_list_templates"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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, so the safety profile is covered. The description adds context beyond that: the `creatable` gate and the free-plan limitation that constrains what the agent can actually do with the results, plus the required scopes (machines:read or images:read) — a genuine auth prerequisite not in the annotations.

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?

Three tight clauses: what is listed, what constrains usability, and what permissions are needed. The core purpose is front-loaded and every sentence carries distinct information with no redundancy.

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?

With no output schema, the description does the work of describing the returned fields (software, default size, creatable flag), which is sufficient for a simple enumerating tool. It could note whether the list is complete or filtered/paginated, but the remaining gap is minor.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies a parameterless full listing and adds no misleading parameter guidance.

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 ("List the templates a machine can start from") and even names concrete example values, which disambiguates it from sibling listing tools like instabox_list_machines or instabox_list_snapshots. The agent knows exactly what collection is returned and what fields accompany it (software, default size).

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 real selection guidance: only templates with `creatable: true` are usable, and the free plan can only create from agent-browser. This effectively routes the agent to check this list before instabox_create_machine. It stops short of explicitly saying "call this before create_machine" or naming the alternative, so not a 5.

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