Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Restart an autopilot

start_autopilot

Restart a stopped autopilot. (uses points, metered on the models used like the website)

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": {
      "autopilot_id": "<autopilot_id>"
    },
    "name": "start_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
autopilot_idYesAutopilot id
idempotency_keyNoOptional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice",
+  "maxLength": 128,
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the write nature (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's real contribution is the cost disclosure: restarts consume points metered on the models used. That is useful context absent from structured fields. However, it does not say what happens if the autopilot is already running, whether prior state/positions are preserved, or why an idempotency_key exists when idempotentHint=false.

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?

Two short sentences, with the core action front-loaded before the cost parenthetical. The parenthetical is conversational and slightly awkward but conveys billing information that would otherwise be missing, so it earns its place.

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 two-parameter tool with full schema coverage, annotations covering the safety profile, and no output schema, the description supplies what structured data lacks: the stopped precondition and the point-cost model. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, with both autopilot_id and idempotency_key fully documented in the schema, so the baseline is 3. The description adds no parameter-level meaning beyond identifying that the autopilot must be in a stopped state to be restarted.

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?

"Restart a stopped autopilot" gives a specific verb (restart) and resource (autopilot), plus the precondition that the target must be stopped, which implicitly separates it from stop_autopilot and create_autopilot. It stops short of explicitly naming a sibling or contrasting behavior with one.

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 phrase "a stopped autopilot" implies the usage condition: call this when an autopilot is halted and you want it running again. There is no explicit when-not guidance and no named alternative for cases such as starting a brand-new autopilot or resuming analysis-type sessions.

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

All SimianX AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources