arcane-cli-mcp

arcane_environments

Read-only

List Arcane Docker host environments with their IDs and default environment, so you can pick the right env_id to pass to other Arcane tools.

Instructions

List Arcane environments (Docker hosts) as a small payload of {id, name, status}, plus the server's default env_id. Call this first and pass the chosen id (or the environment's name) as env_id to arcane_run. An unknown env_id is rejected with the list of known environments.

Example: {}

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": "arcane_environments"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is free to add what they cannot: the exact payload fields, the presence of a default env_id, and the failure semantics that an unknown env_id is rejected with the list of known environments. That error contract is genuinely useful operational detail an agent cannot infer from structured fields.

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-loaded with what is returned, then when to call it, then the failure mode — a sensible order with almost no waste. The trailing "Example: {}" is only marginally useful for a zero-argument tool, which is the main candidate for trimming.

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 zero-parameter, read-only discovery tool with annotations and an output schema, the description covers all an agent needs: purpose, ordering, consumption of the result, and error behavior. Nothing essential is missing or pushed onto the caller to guess.

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?

Zero parameters, so the baseline is 4; the description confirms the no-argument nature with an example invocation of {} and clarifies that the id/name it returns is consumed as env_id elsewhere. No further parameter meaning is possible here.

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?

Names a specific verb and resource ("List Arcane environments (Docker hosts)") and even specifies the returned shape {id, name, status} plus the server default env_id. This distinguishes it immediately from action-oriented siblings like arcane_run or arcane_logs.

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?

Explicitly states call ordering ("Call this first") and the downstream step of passing the chosen id or name as env_id to arcane_run, which is exactly the routing an agent needs. It stops short of any when-not or alternative-listing guidance, so it is clear context rather than a full decision rule.

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

Deploy Server