Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Archive a stopped autopilot

autopilots_delete
Idempotent

Archive an autopilot that is already stopped, to remove it from the list. Stop it first with stop_autopilot; its history is kept and start_autopilot brings it back. Its paper book is left as it is (close it first to be flat).

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": {
      "id": "<id>"
    },
    "name": "autopilots_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=false, idempotentHint=true), the description discloses that the history is retained and the action is reversible, and warns that the paper book is left unchanged. That is exactly the non-obvious side effect an agent needs, though it says nothing about permissions or the response.

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 short sentences, front-loaded with the primary action, then the prerequisite, then the caveat. Nothing is padding, and every clause carries operational information.

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 tool with no output schema, the description covers everything an agent needs: the precondition, the reversibility, the alternative tool, and the one side effect. Annotations already handle the safety profile.

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%, but the sole id parameter's description is only the literal string 'id', and the prose adds nothing about what the id identifies or its format. The baseline 3 applies because the schema nominally documents the parameter and the description does not compensate.

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?

The description states a specific verb and resource (archive an autopilot), plus the precondition (already stopped) and the effect (remove it from the list). This is clearly distinguishable from siblings such as stop_autopilot and start_autopilot.

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?

It explicitly says to stop the autopilot first with stop_autopilot, and points to start_autopilot as the way to bring it back, so the agent has both prerequisites and the reversal path. It also anticipates a related action (close the paper book first to be flat), so there is no ambiguity about the order of operations.

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