Skip to main content
Glama

Soclo

by app.soclo
OverviewDiscussionsAdmin

Remove an actor

soclo_actors_remove
DestructiveIdempotent

Preview the exact actor for approval, then with confirm: true revoke future use. Pass the original actorVersion, the concrete expectedSelectionVersion from soclo_actors_current and a stable clientRequestId. Free. Delayed private cleanup preserves in-flight jobs.

Input Schema

NameRequiredDescriptionDefault
actorIdYesThe owned actor id, from soclo_actors_list.
confirmNoApprove the free preview before true. Stops future use; private cleanup preserves in-flight work.
actorVersionYesThe owned actor’s current actorVersion, from soclo_actors_list.
clientRequestIdYes
expectedSelectionVersionYesThe concrete current selectionVersion, from soclo_actors_current; preserve it with the original request on retries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / definitions
      Added value: +{
+  "s1": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / clientRequestId / $ref
      Added value: +"#/definitions/s1"
    • removedInput schema / properties / clientRequestId / format
      Removed value: -"uuid"
    • removedInput schema / properties / clientRequestId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / clientRequestId / type
      Removed value: -"string"
    • changedInput schema / properties / expectedSelectionVersion / anyOf
      Previous value: -[
-  {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "$ref": "#/definitions/s1"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the operation is free, the preview requires approval before revocation, retries should reuse a stable clientRequestId and preserve expectedSelectionVersion, and delayed private cleanup preserves in-flight jobs. These details clarify safety and lifecycle behavior for a destructive but idempotent operation.

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?

Short and front-loaded: preview/approval comes first, followed by required identifiers and then cost and cleanup behavior. Every sentence contributes operational meaning without waste.

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 destructive, idempotent mutation with no output schema and high schema coverage, the description provides the essential workflow, identifier sourcing, retry stability, cost, and cleanup semantics needed to call it correctly.

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?

Schema coverage is 80%, so the schema carries most parameter meaning. The description still adds useful semantics by specifying that actorVersion must be the original value, expectedSelectionVersion must be concrete from soclo_actors_current, and clientRequestId must be stable across retries.

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 action and resource: preview an actor, then with confirm: true revoke future use. This clearly distinguishes it from sibling tools like soclo_actors_list, soclo_actors_current, soclo_actors_create, and soclo_actors_select.

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?

Explains the required two-step usage pattern: preview for approval, then pass confirm: true to revoke. It also specifies where actorVersion and expectedSelectionVersion should come from, but does not explicitly compare this tool against non-removal alternatives.

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

All Soclo 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