Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Run an autopilot agent now

run_autopilot_agent

Run one of the autopilot's agents now, outside its schedule; the result lands in the event log. (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>",
      "agent": "<agent>"
    },
    "name": "run_autopilot_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
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
Behavior4/5

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

Annotations already establish that this is a non-read-only, open-world, non-destructive operation. The description adds meaningful details beyond that: the call consumes points and is metered on model usage, and the result is written to the event log rather than returned directly. It does not cover auth requirements, failure modes, or whether running an agent changes autopilot state.

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?

The description is two compact sentences with the primary action and timing constraint front-loaded. The parenthetical cost note is relevant, though slightly informal with 'like the website,' and no space is wasted restating the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a metered, open-world mutation with no output schema, the description usefully covers the point cost and where the result lands. It still leaves the agent-type semantics and execution preconditions unexplained, which matter for calling the correct agent correctly.

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?

The schema documents autopilot_id and provides a detailed idempotency_key definition, so about two thirds of parameter meaning is already structured. The agent enum's four values (indicator, intelligence, fundamental, decision) are not explained in either the schema or the description, and the description only says 'one of the autopilot's agents,' adding little semantic clarity.

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?

The description names a specific action (run) and resource (one of the autopilot's agents) and clarifies that it is triggered manually, outside the schedule. The purpose is unambiguous, though it does not explicitly identify which sibling tool to use instead.

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?

'Outside its schedule' provides useful context for when to use this tool, implying immediate manual execution. However, there is no explicit when-not guidance versus siblings such as start_autopilot, autopilot_action, or run_live_analysis, and no stated prerequisites like the autopilot being active.

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