Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Lifecycle and delivery log

autopilots_logs
Read-onlyIdempotent

Lifecycle and delivery log of one autopilot (started, stopped, paused, webhook deliveries): use when an autopilot stopped unexpectedly or updates did not arrive.

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

Input Schema

NameRequiredDescriptionDefault
idYesid
limitNo<= 200 (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "<= 200 (default 50)",
+  "type": "integer"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the description only needs to add context. It usefully discloses that webhook delivery records are included alongside lifecycle state changes, which hints at diagnostic value, but says nothing about retention window, ordering, or whether delivery entries include error details.

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?

A single sentence with the resource and the diagnostic use case front-loaded, and no filler. Every clause (log content, then trigger condition) earns its place.

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

Completeness4/5

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

For a two-parameter read-only log tool with no output schema, the description gives enough to call it correctly and interpret the kinds of entries returned. It could go slightly further on ordering or expected entry shape, but the gap is small given annotation coverage.

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% for both parameters, so the schema already documents 'id' and 'limit'. The description only implies that the target is a single autopilot ('of one autopilot') and adds no detail on the id format or the meaning/behavior of the limit default.

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?

States a specific resource ('Lifecycle and delivery log of one autopilot') and enumerates what it contains (started, stopped, paused, webhook deliveries). An agent can tell it is a per-autopilot diagnostic log rather than an action or analysis tool, though it does not name a sibling to contrast with.

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?

Gives a concrete triggering condition: 'use when an autopilot stopped unexpectedly or updates did not arrive.' That is a clear when-to-use signal, but there are no explicit exclusions or named alternatives for closely related tools such as the autopilot events or get_autopilot endpoints.

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