Skip to main content
Glama

Take a picture of the project in the user's open R3 editor

r3_editor_capture
Read-only

Capture the canvas of a project open in the user's R3 editor — the scene as it looks NOW, running physics included — and LOOK at it: the answer is an image. Call it after a visual change (r3_editor_set, r3_editor_create, r3_editor_code …) to check what you built, and after r3_editor_run to see it move. By default (camera: "editor") it is what the user sees: the editor's view camera, edit aids included. camera: "project" takes it through the project's own camera instead, with no edit aids, as a visitor sees it: use that to check a camera or a camera script. At most 1280 px each way (width, default 1024); a JPEG. Needs project:read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "r3_editor_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNoThe picture's largest width in px, 64..1280 (default 1024); it keeps the canvas's aspect and is never scaled up.
cameraNoWhose view: "editor" (default) = the editor's view camera the user looks through, edit aids included; "project" = the project's own camera, no edit aids, as a visitor sees it (check a camera script with it).
projectIdYesA project open in the user's editor (r3_whoami lists them).

Output Schema

NameRequiredDescriptionDefault
bytesYes
widthYes
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.
cameraYes
editorYes
heightYes
mimeTypeYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / camera
      Added value: +{
      +  "description": "Whose view: \"editor\" (default) = the editor's view camera the user looks through, edit aids included; \"project\" = the project's own camera, no edit aids, as a visitor sees it (check a camera script with it).",
      +  "enum": [
      +    "editor",
      +    "project"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / camera
      Added value: +{
      +  "enum": [
      +    "editor",
      +    "project"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "width",
      -  "height",
      -  "mimeType",
      -  "bytes",
      -  "editor",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "camera",
      +  "width",
      +  "height",
      +  "mimeType",
      +  "bytes",
      +  "editor",
      +  "answer"
      +]
  2. 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"
      +  }
      +]
  3. 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",
      -  "width",
      -  "height",
      -  "mimeType",
      -  "bytes",
      -  "editor"
      -]New value: +[
      +  "projectId",
      +  "width",
      +  "height",
      +  "mimeType",
      +  "bytes",
      +  "editor",
      +  "answer"
      +]
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real context beyond that — the response is an image, it is a JPEG capped at 1280 px, the default view includes edit aids, and it requires project:read. It stops short of describing latency or failure modes (e.g. what happens if the editor is closed), which keeps it from a 5.

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?

Front-loaded with the core action and the fact that the answer is an image, then usage, then mode semantics, then constraints. It is dense and largely earned, though the camera-mode explanation is duplicated almost verbatim in the schema, and the parenthetical chain ('r3_editor_set, r3_editor_create, r3_editor_code …') is slightly sprawling.

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 read-only capture tool with annotations, a full output schema, and complete parameter documentation, nothing material is missing: the agent knows what it gets (an image), how to select the view, the size ceiling, the auth scope, and when in a workflow to call it.

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 already 100%, so the baseline is 3, but the description adds interpretation: 'editor' means what the user sees with edit aids, 'project' means a visitor's view with no edit aids, and width caps at 1280 px with a 1024 default. The width behavior ('never scaled up', aspect preserved) is echoed from the schema, so the added value is modest rather than substantial.

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 concrete verb and resource — 'Capture the canvas of a project open in the user's R3 editor' — and immediately pins down what is captured (the live scene, physics included) and what comes back (an image). This separates it cleanly from siblings like r3_editor_inspect, r3_image_create, and r3_editor_set_preview_image.

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

Usage Guidelines5/5

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

Explicitly names the trigger conditions (after r3_editor_set, r3_editor_create, r3_editor_code to verify a build; after r3_editor_run to see motion) and names the alternative mode with its own use case ('camera: "project"' to check a camera or camera script). When-to-use, which sibling precedes it, and the mode-selection rule are all given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources