Skip to main content
Glama

static.md

by md.static
OverviewDiscussionsAdmin

Create a whiteboard

create_board

Creates an Excalidraw whiteboard owned by the signed-in user, optionally seeded with a scene and in a folder, and returns its link. Free plan boards hold up to 300 elements. New boards open to anyone with the link.

Input Schema

NameRequiredDescriptionDefault
titleNoShort title (static.md keeps the first 32 characters)
folderNoFolder to put the whiteboard in, such as "work/launch"; it is made if it doesn't exist yet. A folder the user already has can be given exactly as the list tools show it, spaces included. Default: the top level ("/")
excalidraw_jsonNoAn Excalidraw scene export ({"elements": [...]}) or an array of Excalidraw elements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / folder / description
      Previous value: -"Folder to put the whiteboard in, such as \"work/launch\"; it is made if it doesn't exist yet. Default: the top level (\"/\")"New value: +"Folder to put the whiteboard in, such as \"work/launch\"; it is made if it doesn't exist yet. A folder the user already has can be given exactly as the list tools show it, spaces included. Default: the top level (\"/\")"
  2. Changed1 schema field changed
    • addedInput schema / properties / folder
      Added value: +{
+  "description": "Folder to put the whiteboard in, such as \"work/launch\"; it is made if it doesn't exist yet. Default: the top level (\"/\")",
+  "maxLength": 700,
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing ownership, return value (the board link), the free-plan element cap, and the important default that new boards open to anyone with the link. These are material behavioral facts an agent would not otherwise know, especially the sharing default, without contradicting the non-destructive/non-idempotent annotations.

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?

Three compact sentences, front-loaded with the core action and scope. Each sentence adds distinct value: purpose, free-plan limit, and default sharing behavior.

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?

Given no output schema, the description correctly states that the tool returns the board link. It also covers ownership, optional scene/folder behavior, plan limits, and the default sharing state, leaving no major behavioral gap for an agent calling this creation tool.

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 the schema already explains title, folder creation, and the accepted Excalidraw scene format. The description mentions optional scene seeding and folder placement but adds no syntax or constraints beyond what the schema provides, making the baseline 3 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: creates an Excalidraw whiteboard owned by the signed-in user. This clearly distinguishes it from sibling creation tools such as create_note, which produce a different artifact type.

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?

The description implies when to use it by naming the artifact type and optional seeding/folder behavior, but it never explicitly says 'use this when' or contrasts it with siblings like create_note. An agent can infer the use case, but no exclusions or alternatives are provided.

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

All static.md toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources