Soclo

Pause Autopilot

soclo_autopilot_pause

DestructiveIdempotent

Pause Autopilot so no new daily work is scheduled until it is enabled again. 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. 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/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: 'Free' (no cost), required permission 'manage:autopilot', the preview-on-first-call confirmation flow, 'Starts no run', and a retry-safety rule for uncertain outcomes. These are exactly the behavioral facts annotations cannot convey. The pause mutation is consistent with destructiveHint=true and the no-automatic-retry guidance fits idempotentHint=true.

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?

Purpose is front-loaded in the first clause, and each subsequent sentence adds a distinct operational fact (cost, params, preview, permission, retry rule). It is dense but not padded; the only minor weakness is a run-on feel from packing many facts into single sentences.

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?

Covers the mutation's semantics, auth, cost, confirmation flow, and retry policy well, and no output schema means return values needn't be described. However, for a tool with a large nested 'patch' object at 0% schema coverage, the complete omission of that parameter leaves a real gap an agent would need filled.

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 description coverage is 0%, so the description must compensate, and it does for three of four params: expectedUpdatedAt (source it from soclo_autopilot_read), clientRequestId (stable UUID), and confirm (preview vs execute). The large, deeply nested 'patch' object is entirely undocumented, leaving the most complex parameter unexplained.

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 verb and resource ('Pause Autopilot') plus the concrete effect: 'no new daily work is scheduled until it is enabled again'. The 'until it is enabled again' phrasing implicitly routes to the enable sibling. It does not explicitly name soclo_autopilot_off, so the boundary against the other stop-style tool is left to inference.

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 actionable procedural guidance: pass expectedUpdatedAt from soclo_autopilot_read, supply a stable clientRequestId, and the first call without confirm:true returns a preview. It also advises reading current state and reconciling after uncertainty instead of auto-retrying. It stops short of explicitly contrasting with soclo_autopilot_off or saying when pausing is preferable.

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?