arcane-cli-mcp

arcane_cli_help

Read-only

Displays the exact subcommands, positional arguments, and flags for the installed arcane-cli version. Check it before running commands when you are unsure about renamed or changed flags.

Instructions

Show arcane-cli <command...> --help: the exact subcommands, positional arguments and flags of the CLI version installed on this server. Use it before arcane_run whenever you are unsure of a command or flag. The CLI is in early development and flags get renamed, so check rather than guess. For concepts and how-to guides use arcane_docs instead.

Examples:

{"command": []} (top-level command groups)
{"command": ["projects"]} (project subcommands)
{"command": ["images", "vulnerabilities", "ignore"]}

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

Input Schema

Name	Required	Description	Default
`command`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the output reflects the CLI version installed on this specific server, and the CLI is in early development so flags may be renamed, which tells the agent results are version-dependent and worth re-checking. It does not discuss output shape, but an output schema exists, so this is a minor omission.

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?

Front-loaded with the action and the routing rule before any examples, and the examples are compact, aligned, and annotated with parenthetical explanations. Every sentence carries information an agent needs; nothing is padding.

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 one-parameter, read-only lookup tool with annotations and an output schema already supplied, the description covers purpose, timing, alternatives, version-dependence, and argument-path semantics. Nothing an agent needs in order to invoke it correctly is missing.

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 0% and the single `command` parameter is undocumented in the schema, so the description must compensate. The three worked examples do exactly that: an empty array means top-level command groups, a one-element array drills into subcommands, and a multi-element array walks a nested path. Only the meaning of the null default is left implicit.

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: shows `arcane-cli <command...> --help` output, i.e. the exact subcommands, positional arguments and flags of the CLI version installed on this server. It also explicitly distinguishes itself from arcane_run (execution) and arcane_docs (concepts/how-to), so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it before arcane_run whenever you are unsure of a command or flag'), a rationale ('flags get renamed, so check rather than guess'), and names the alternative for a different need ('For concepts and how-to guides use arcane_docs instead'). Both when-to-use and when-not-to-use are covered.

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

Deploy Server