Field Service Business Platform by Doing Work

schedule_removeOpenSlot

Take back an open time that is not booked yet (owner or office).

Input Schema

Name	Required	Description	Default
`shop_id`	Yes
`slot_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "properties": {
-      "data": {
-        "items": {
-          "properties": {
-            "booked": {
-              "type": "boolean"
-            },
-            "ends_at": {
-              "format": "date-time",
-              "type": "string"
-            },
-            "request_id": {
-              "format": "uuid",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "slot_id": {
-              "format": "uuid",
-              "type": "string"
-            },
-            "starts_at": {
-              "format": "date-time",
-              "type": "string"
-            }
-          },
-          "required": [
-            "slot_id",
-            "starts_at",
-            "ends_at",
-            "booked"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "data"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "approval_id": {
-        "format": "uuid",
-        "type": "string"
-      },
-      "approval_required": {
-        "enum": [
-          true
-        ],
-        "type": "boolean"
-      },
-      "expires_at": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "status": {
-        "enum": [
-          "pending"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "approval_required",
-      "approval_id",
-      "status",
-      "expires_at",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "data": {
+        "items": {
+          "properties": {
+            "booked": {
+              "type": "boolean"
+            },
+            "ends_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "kind": {
+              "enum": [
+                "routine",
+                "emergency"
+              ],
+              "type": "string"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "slot_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "starts_at": {
+              "format": "date-time",
+              "type": "string"
+            }
+          },
+          "required": [
+            "slot_id",
+            "starts_at",
+            "ends_at",
+            "booked",
+            "kind"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "data"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "approval_id": {
+        "format": "uuid",
+        "type": "string"
+      },
+      "approval_required": {
+        "enum": [
+          true
+        ],
+        "type": "boolean"
+      },
+      "expires_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "pending"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "approval_required",
+      "approval_id",
+      "status",
+      "expires_at",
+      "message"
+    ],
+    "type": "object"
+  }
+]

First observedNov 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. It offers one useful precondition — the slot must not be booked — but says nothing about what happens if the slot is booked, whether removal is reversible, what permissions are required, or what side effects occur for already-assigned visits.

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?

A single tight sentence with no filler; the key constraint (not booked yet) is placed inline rather than buried. It is arguably under-specified rather than overly long, and the trailing parenthetical adds ambiguity rather than information.

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

Completeness2/5

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

For a mutation on scheduling data with no annotations, omitted parameters, and only an output schema for returns, the definition leaves critical gaps: failure behavior on booked slots, permission requirements, and interaction with existing visits or routes are all unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both required parameters (shop_id, slot_id) have 0% schema description coverage and the description says nothing about them. Their UUID formats and names make them largely self-explanatory, but there is no added meaning such as whether slot_id is scoped to the shop or what happens on a mismatched pair.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Take back an open time that is not booked yet" identifies the resource (an open, unbooked slot) and implies a removal, but the verb is idiomatic rather than precise, and "(owner or office)" is ambiguous — it is unclear whether it names a permission scope, an actor, or a slot type. It never contrasts with schedule_addOpenSlots or schedule_openSlots, so the agent must infer this is the inverse of adding a slot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit statement of when to use this versus schedule_addOpenSlots, schedule_openSlots, or visits_cancel. The only contextual hint is the aside "(owner or office)", which is unexplained and does not function as usable guidance.

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

All Field Service Business Platform by Doing Work 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?