Skip to main content
Glama

read_scene

Read-onlyIdempotent

Retrieves the complete current Excalidraw scene, including images, element IDs, versions, and a scene revision so clients can co-edit with update_elements using accurate IDs and versions.

Instructions

Read the complete current .excalidraw scene, including image files, element IDs/versions and a scene revision. Use IDs and versions with update_elements for ordinary co-editing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the return contents (image files, element IDs/versions, scene revision) and the versioning contract that makes safe updates possible. It does not mention payload size or cost of reading a large scene, which is the main remaining gap.

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?

Two sentences, front-loaded with what is read and followed by the action it enables. No filler, no restatement of the tool name, and the workflow hint is placed where it is most useful.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing return content, and it does name the key components returned. It is nearly complete for a parameterless read tool, though it could say more about response shape or how large the payload may be.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a 0-param tool applies. The mention of element IDs and revision refers to returned data rather than inputs, which is appropriate.

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 and resource ("Read the complete current .excalidraw scene") and enumerates the payload (image files, element IDs/versions, scene revision), which lets an agent distinguish it from siblings like screenshot or export_svg without opening a 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 explicit downstream guidance: "Use IDs and versions with update_elements for ordinary co-editing," which implicitly frames this as the read step before an edit. It stops short of naming when to prefer replace_scene or screenshot instead, so there are no explicit exclusions.

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