Skip to main content
Glama
bjcoombs

excalidraw-room-mcp

by bjcoombs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_mentions

Find unacknowledged mentions addressed to you on a shared Excalidraw canvas, along with nearby elements. Optionally include already-handled mentions to locate and clean up notes.

Instructions

List every pending (unacknowledged) mention addressed to this agent on the canvas right now, each with its nearby elements. With no tag it answers to its own handle and to the '@claude' broadcast tag. Mentions surfaced here are marked seen on the canvas as wait_for_mention does; pass autoSeen false to look without touching the drawing. Pass includeHandled true to also list the notes this server acknowledged and left on the canvas, marked handled, so they can be found and cleaned up.

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 each 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.
includeHandledNoAlso list mentions already acknowledged whose note is still on the canvas (kept with a check mark, a status or a reply). They are listed after the pending ones with 'handled' on the first line, and are never marked seen.
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
    • addedInput schema / properties / radius / description
      Added value: +"How far around each 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. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / includeHandled
      Added value: +{
+  "default": false,
+  "description": "Also list mentions already acknowledged whose note is still on the canvas (kept with a check mark, a status or a reply). They are listed after the pending ones with 'handled' on the first line, and are never marked seen.",
+  "type": "boolean"
+}
  4. 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, the description takes on full behavioral disclosure. It explicitly states that surfaced mentions are 'marked seen on the canvas', explains how to avoid that side effect with autoSeen false, and clarifies that handled notes remain on the canvas as acknowledged notes. This is strong transparency for a tool with mutation-like 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?

Three sentences carry the full message: purpose, default tag behavior, and side-effect/option semantics. There is no filler, and the most important scoping information is front-loaded in the first sentence.

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?

For a 5-parameter tool with no annotations and no output schema, the description covers the core return concept ('each with its nearby elements'), the main side effect, and the optional behaviors needed for safe invocation. The remaining parameter details (radius, answerAgentMentions) are fully documented in the schema, so the combined package is complete.

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 description coverage is 100%, so the baseline is 3 and the description does not need to repeat parameter syntax. It adds value by explaining the no-tag default behavior ('answers to its own handle and to the @claude broadcast tag'), the effect of autoSeen, and the cleanup motivation for includeHandled.

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: 'List every pending (unacknowledged) mention addressed to this agent on the canvas right now, each with its nearby elements.' This clearly separates it from waiting-style siblings by emphasizing 'right now' and from acknowledge_mention by restricting to 'pending (unacknowledged)' mentions.

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 positions the tool as a non-blocking snapshot by saying 'right now' and comparing its behavior to wait_for_mention. It also gives concrete guidance for autoSeen false ('look without touching the drawing') and includeHandled ('so they can be found and cleaned up'). It does not explicitly enumerate when to prefer poll_room or acknowledge_mention, so it stops short of a perfect 5.

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