Skip to main content
Glama
Sign In

R3

by org.r3js
OverviewDiscussionsAdmin

Stop the project in the user's open R3 editor

r3_editor_stop
Idempotent

Press the Stop buttons of the user's open R3 editor: stop physics, code, audio and music (all of them, or the ones named in systems), exactly as the user's own click does. Stopping physics puts every body back where it was placed. Changes nothing saved. Needs the editor:run right.

Input Schema

NameRequiredDescriptionDefault
systemsNoWhich of the editor's Run / Stop buttons: physics, code, audio, music. Leave out for all of them.
projectIdYesA project open in the user's editor (r3_whoami lists them).

Output Schema

NameRequiredDescriptionDefault
actionYes
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
editorYes
systemsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / editor / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "lastActiveAgoMs": {
-        "type": "number"
-      },
-      "lastActiveAt": {
-        "type": "string"
-      },
-      "openProjects": {
-        "anyOf": [
-          {
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "id": {
-                  "type": "string"
-                },
-                "name": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                }
-              },
-              "required": [
-                "id",
-                "name"
-              ],
-              "type": "object"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "openedAt": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "openedAt",
-      "lastActiveAt",
-      "lastActiveAgoMs",
-      "openProjects"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "frames": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "advancing": {
+                "type": "boolean"
+              },
+              "frameSeen": {
+                "type": "boolean"
+              },
+              "sceneShown": {
+                "type": "boolean"
+              },
+              "visible": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "advancing",
+              "visible",
+              "sceneShown",
+              "frameSeen"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "lastActiveAgoMs": {
+        "type": "number"
+      },
+      "lastActiveAt": {
+        "type": "string"
+      },
+      "openProjects": {
+        "anyOf": [
+          {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "id",
+                "name"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "openedAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "openedAt",
+      "lastActiveAt",
+      "lastActiveAgoMs",
+      "openProjects"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
+  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "projectId",
-  "action",
-  "systems",
-  "editor"
-]New value: +[
+  "projectId",
+  "action",
+  "systems",
+  "editor",
+  "answer"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare non-readOnly, idempotent and non-destructive, and the description adds context those cannot carry: the physics side effect ('puts every body back where it was placed'), a persistence guarantee ('Changes nothing saved'), and an authorization requirement (editor:run right). It is consistent with, and strictly additive to, the annotation set.

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?

Four short sentences, front-loaded with the action, followed by scope, side effects, persistence and prerequisite in descending order of need. No sentence is redundant padding; the parenthetical qualifier on `systems` earns its space by clarifying the all-vs-named choice.

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?

With an output schema present, return values need no explanation, and the annotations cover safety. The description supplies the remaining pieces an agent needs: permission requirement, scope selection, side effect on physics bodies, and the guarantee that nothing is persisted.

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 100%, so both parameters are already documented. The description restates the `systems` semantics ('all of them, or the ones named in `systems`') without adding new syntax, ordering or default behavior beyond what the schema and its enum-like value list provide. Baseline 3 applies.

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 ('Stop') and resource ('the user's open R3 editor'), enumerates exactly what gets stopped (physics, code, audio, music), and is unmistakably the inverse of the sibling r3_editor_run. An agent can tell what it does and what it does not do without opening the schema.

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 clear prerequisite ('Needs the editor:run right') and frames invocation as equivalent to the user's own Stop click, which tells the agent when calling it is appropriate. It never names r3_editor_run as the counterpart in an explicit 'to do X instead, use Y' form, so it stops short of full routing guidance.

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

All R3 toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources