Skip to main content
Glama
bjcoombs

excalidraw-room-mcp

by bjcoombs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wait_for_mention

Block until a text note addressed to you appears on the Excalidraw canvas, then return it with nearby elements. Poll repeatedly to catch mentions until timeout.

Instructions

Block until someone writes a text element addressed to this agent on the canvas, then return it with the elements around it. With no tag it answers to its own handle and to the '@claude' broadcast tag. Returns 'no mention' after timeoutSeconds so the caller can loop. A mention is reported once it has stopped changing for about 1.5s. Returning it also marks it seen on the canvas (amber stroke and a marker) so the person knows the note landed; pass autoSeen false to poll without touching the drawing. Acknowledge it with acknowledge_mention when done, which removes the handled note from the canvas; reply about the work in chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoText a note must contain to count as a mention. Omit it and this server answers to its own handle - "@<handle>", the handle room_status reports - and to "@claude", the broadcast tag every agent in the room hears; matching is case-insensitive. Pass a tag to match that text alone, which is how you read notes addressed to someone else.
radiusNoHow far around the mention to look for related elements, in canvas px. Defaults to the room's nearbyRadius.
autoSeenNoMark the mention seen on the canvas (amber stroke plus a marker) as soon as it is returned. Set false for silent polling.
timeoutSecondsNo
answerAgentMentionsNoAlso return notes written by another agent in the room. False by default: a note stamped with another agent's handle is dropped, while notes people wrote (nothing stamps them) and this server's own notes are always returned. True returns them all, each with the 'from: <handle>' line naming its author - up to the room's agentReplyDepth, which bounds how far a chain an agent started may run before this agent stops hearing it. A chain a person started is never bounded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / answerAgentMentions / description
      Previous value: -"Also return notes written by another agent in the room. False by default: a note stamped with another agent's handle is dropped, while notes people wrote (nothing stamps them) and this server's own notes are always returned. True returns them all, each with the 'from: <handle>' line naming its author."New value: +"Also return notes written by another agent in the room. False by default: a note stamped with another agent's handle is dropped, while notes people wrote (nothing stamps them) and this server's own notes are always returned. True returns them all, each with the 'from: <handle>' line naming its author - up to the room's agentReplyDepth, which bounds how far a chain an agent started may run before this agent stops hearing it. A chain a person started is never bounded."
  2. Changed5 schema fields changedv0.7.1
    • addedInput schema / properties / answerAgentMentions
      Added value: +{
+  "default": false,
+  "description": "Also return notes written by another agent in the room. False by default: a note stamped with another agent's handle is dropped, while notes people wrote (nothing stamps them) and this server's own notes are always returned. True returns them all, each with the 'from: <handle>' line naming its author.",
+  "type": "boolean"
+}
    • removedInput schema / properties / radius / default
      Removed value: -250
    • changedInput schema / properties / radius / description
      Previous value: -"How far around the mention to look for related elements, in canvas px."New value: +"How far around the mention to look for related elements, in canvas px. Defaults to the room's nearbyRadius."
    • removedInput schema / properties / tag / default
      Removed value: -"@claude"
    • addedInput schema / properties / tag / description
      Added value: +"Text a note must contain to count as a mention. Omit it and this server answers to its own handle - \"@<handle>\", the handle room_status reports - and to \"@claude\", the broadcast tag every agent in the room hears; matching is case-insensitive. Pass a tag to match that text alone, which is how you read notes addressed to someone else."
  3. Addedv0.4.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it well: it discloses blocking with timeout, the 1.5s stability requirement, canvas side effects (amber stroke and marker), the autoSeen opt-out, and the fact that acknowledge_mention removes the handled note. This gives an agent a realistic model of the tool's behavior and side effects.

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 dense but every sentence adds a distinct behavioral fact: blocking semantics, tag matching, timeout looping, stability delay, seen-marking side effect, and the acknowledge workflow. It is front-loaded with the core operation and then expands into parameter-specific details without redundancy.

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 five parameters, no annotations, and no output schema, this description is remarkably complete. It explains when the tool returns, what counts as a mention, how to poll silently, how to respond, and what side effects occur on the canvas. An agent has enough context to invoke it correctly and understand the full lifecycle.

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 already high at 80%, but the description adds meaning beyond the schema: it explains tag matching semantics, radius defaults to nearbyRadius, autoSeen's visual effect, and the author/chain behavior of answerAgentMentions. timeoutSeconds has no schema description, but the main description mentions the 'no mention' return after timeout, and the schema provides bounds and default.

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 opens with a specific verb and resource: 'Block until someone writes a text element addressed to this agent on the canvas, then return it with the elements around it.' This clearly distinguishes wait_for_mention from non-blocking list/poll siblings, and the final sentence connects it to acknowledge_mention as the follow-up cleanup tool.

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?

The description gives clear conditions: no tag means the agent's own handle and '@claude', a custom tag reads mentions addressed to someone else, autoSeen false is for silent polling, and acknowledge_mention should be called when done. It does not explicitly state when to prefer siblings like list_mentions or poll_room, so the guidance is strong but not exhaustive.

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

Deploy Server

Other Tools