Skip to main content
Glama

append_elements

Add new Excalidraw element skeletons while preserving the current drawing; supports labeled shapes, styled text, and point-based arrows. Read the scene before retrying after errors.

Instructions

Add Excalidraw element skeletons while preserving the existing drawing. Shapes support label:{text}; text supports text,fontSize; arrows support points:[[0,0],[dx,dy]]. IDs are regenerated. This is not idempotent: read the scene before retrying after an error.

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

Input Schema

NameRequiredDescriptionDefault
elementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations it adds two non-obvious behaviors: IDs are regenerated, and the non-idempotency is paired with a recovery procedure (read the scene before retrying). That is real added context rather than a restatement of idempotentHint=false. It could still say more about ordering or partial-failure behavior.

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 purpose, then type-specific syntax, then the failure-mode warning. No filler, and the most consequential caveat is placed last for emphasis.

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?

For a one-parameter tool with no output schema, this covers purpose, supported element payloads, ID regeneration, and non-idempotency handling. The remaining gap is minor: no mention of what the response returns or ordering of appended elements.

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 0%, so the description must carry parameter meaning, and it does: it documents per-element-type payloads (label for shapes, text/fontSize for text, points pairs for arrows) that the schema's bare additionalProperties leaves undefined. Required x/y/type are covered by the schema itself rather than the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Add Excalidraw element skeletons') and immediately clarifies the scope constraint ('while preserving the existing drawing'), which separates it from a full-scene replacement. It does not name the sibling alternative (replace_scene) explicitly, so it stops just short of a 5.

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

Usage Guidelines3/5

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

Gives one concrete usage rule — read the scene before retrying after an error — which is genuinely actionable. It does not say when to prefer this over update_elements or replace_scene, so guidance on alternatives is only implied by the 'preserving' phrasing.

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