excalidraw-mcp-obsidian

Overview Schema Source Related Servers Discussions Admin

snapshot_scene

Preserve the current Excalidraw canvas by saving a named snapshot, enabling you to capture and restore diagram states at any point.

Instructions

Save a named snapshot of the current canvas state

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": {
      "name": "<name>"
    },
    "name": "snapshot_scene"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations to fall back on, the description should disclose behavioral traits. It does not mention overwrite behavior, error conditions, return values, or any side effects beyond saving. It adds the scope 'current canvas state' but leaves key behaviors unclear.

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?

The description is a single concise sentence with no redundant words. It is front-loaded with the primary verb and resource, making it easy to parse.

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

Completeness3/5

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

For a low-complexity tool with one parameter and no output schema, the description is adequate for basic invocation but lacks details on overwrite behavior, return values, or storage semantics. It is complete enough to understand the core action but leaves gaps that could affect agent decision-making.

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 schema has 0% description coverage for the 'name' parameter, but the tool description says 'named snapshot', which clarifies that the name parameter is the identifier for the snapshot. This adds meaningful semantics beyond the schema, though it does not specify any constraints or uniqueness rules.

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?

The description clearly states the verb 'save' and the resource 'a named snapshot of the current canvas state', distinguishing it from siblings like restore_snapshot, export_scene, and import_scene. It is specific about the action and scope.

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?

The description only states what the tool does and does not provide guidance on when to use it compared to alternatives. There is no mention of exclusions, prerequisites, or when to prefer another tool such as export_scene.

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