Soclo

Switch Autopilot off

soclo_autopilot_off

DestructiveIdempotent

Switch Autopilot off (manual mode) so no future daily work is planned. Free. Pass the exact expectedUpdatedAt from soclo_autopilot_read and a stable UUID clientRequestId; the first call without confirm:true returns a preview. Starts no run and keeps existing plan and Ads Watch billing. Needs manage:autopilot. After uncertainty read current state and reconcile instead of retrying automatically.

Input Schema

Name	Required	Description	Default
`patch`	No
`confirm`	No
`clientRequestId`	No
`expectedUpdatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 25, 2026
- addedInput schema / definitions
```
Added value: +{
+  "s1": {
+    "additionalProperties": false,
+    "properties": {
+      "override": {
+        "enum": [
+          "manual",
+          "assist",
+          "autopilot"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+}
```
- addedInput schema / properties / patch / properties / domains / properties / ads / $ref
```
Added value: +"#/definitions/s1"
```
- removedInput schema / properties / patch / properties / domains / properties / ads / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / patch / properties / domains / properties / ads / properties
```
Removed value: -{
-  "override": {
-    "enum": [
-      "manual",
-      "assist",
-      "autopilot"
-    ],
-    "type": "string"
-  }
-}
```
- removedInput schema / properties / patch / properties / domains / properties / ads / type
```
Removed value: -"object"
```
- addedInput schema / properties / patch / properties / domains / properties / growth / $ref
```
Added value: +"#/definitions/s1"
```
- removedInput schema / properties / patch / properties / domains / properties / growth / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / patch / properties / domains / properties / growth / properties
```
Removed value: -{
-  "override": {
-    "enum": [
-      "manual",
-      "assist",
-      "autopilot"
-    ],
-    "type": "string"
-  }
-}
```
- removedInput schema / properties / patch / properties / domains / properties / growth / type
```
Removed value: -"object"
```
- addedInput schema / properties / patch / properties / domains / properties / posting / $ref
```
Added value: +"#/definitions/s1"
```
- removedInput schema / properties / patch / properties / domains / properties / posting / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / patch / properties / domains / properties / posting / properties
```
Removed value: -{
-  "override": {
-    "enum": [
-      "manual",
-      "assist",
-      "autopilot"
-    ],
-    "type": "string"
-  }
-}
```
- removedInput schema / properties / patch / properties / domains / properties / posting / type
```
Removed value: -"object"
```
Changed5 schema fields changedOct 19, 2026
- addedInput schema / properties / patch / properties / guardrails / properties / allowMotionEffects
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / patch / properties / guardrails / properties / dailyCreditCap
```
Removed value: -{
-  "maximum": 2147483647,
-  "minimum": 0,
-  "type": "integer"
-}
```
- removedInput schema / properties / patch / properties / guardrails / properties / monthlyCreditCap
```
Removed value: -{
-  "maximum": 2147483647,
-  "minimum": 0,
-  "type": "integer"
-}
```
- addedInput schema / properties / patch / properties / guardrails / properties / recipe / properties / cadenceStartDay
```
Added value: +{
+  "maximum": 6,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedInput schema / properties / patch / properties / guardrails / properties / recipe / properties / captionsPerWeek
```
Added value: +{
+  "maximum": 2147483647,
+  "minimum": 0,
+  "type": "integer"
+}
```
First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the destructive/idempotent annotations by stating it is free, starts no run, preserves the existing plan and Ads Watch billing, requires manage:autopilot, and previews before committing. The recovery advice ('After uncertainty read current state and reconcile instead of retrying') is exactly what an agent needs for a destructive-but-idempotent mutation.

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?

Six short clauses with the effect first, then the mechanics, then the safety notes; no filler and nothing buried behind a preamble.

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?

Covers cost, side effects, auth, preview flow and error recovery for a destructive mutation with no output schema. Only gap is the unaddressed patch object, which likely should be documented as ignored or optional.

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?

With 0% schema coverage the description must carry the load, and it explains expectedUpdatedAt's source (exact value from soclo_autopilot_read), clientRequestId stability, and confirm's preview/commit semantics. The large nested 'patch' object is never mentioned, leaving one parameter unexplained.

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 ('Switch Autopilot off (manual mode)') plus the effect ('no future daily work is planned'), which distinguishes it from soclo_autopilot_enable, soclo_autopilot_pause and soclo_autopilot_run without consulting their schemas.

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?

Tells the agent to read state first via soclo_autopilot_read, to send a stable clientRequestId, and that a call without confirm:true yields a preview, so the when/how is clear. It does not explicitly contrast with soclo_autopilot_pause, which would have been the natural alternative to rule out.

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

All Soclo tools Inspect

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

Need Help?