sketchdex

Overview Schema Source Related Servers Discussions Admin

check_scene

Find layout problems by geometry in an Excalidraw scene—hidden text, overflow, zero-size elements, broken bindings, strays, duplicates—and return element ids for fixes.

Instructions

Find layout problems by geometry instead of by looking: text hidden behind a filled shape drawn after it, captions running past the panel they sit in, labels too tall for their container, zero-size elements, broken arrow bindings, strays parked far off, exact duplicates. Each finding carries the element ids, so the fix is one update_elements call. Run it after a batch of drawing - it is far cheaper than a render and catches what a render would only show you if you looked closely.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max findings (default 60).
`scene`	Yes	Scene id, exact name, or a unique part of the name. Use list_scenes if unsure.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations present, the description carries the burden and does so well: it discloses the diagnostic (non-mutating) nature, the return shape ('each finding carries the element ids'), and the cost model relative to rendering. It does not state any permission or rate-limit caveats, but for a read-only analysis tool this covers the essentials.

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 purpose, then the finding list, then the workflow advice. The example enumeration is long but each entry is a distinct, useful category rather than filler. Minor length, no wasted sentences.

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?

No output schema exists, so the description correctly notes the return content (element ids) and the follow-up action. Combined with fully documented params, an agent has what it needs to invoke and act on results; only cost/limit edge behavior is left implicit.

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 (scene, limit) are already documented, including the default of 60 and the list_scenes fallback. The description adds no parameter-level syntax or format detail, so the baseline of 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 (find) and resource (layout problems, by geometry), and enumerates concrete finding classes (occluded text, overflowing captions, oversized labels, zero-size elements, broken arrow bindings, strays, duplicates). An agent can immediately distinguish it from render_scene and update_elements.

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 clear timing ('Run it after a batch of drawing') and a direct alternative comparison ('far cheaper than a render'). It names update_elements as the remediation path. No explicit when-not guidance, but the context is unambiguous.

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