excalidraw-mcp-obsidian

by zzmkxd

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

query_elements

Find Excalidraw elements in Obsidian diagrams using filters for type, bounding box, or custom criteria.

Instructions

Query Excalidraw elements with optional filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_elements"
  }
}

Input Schema

Name	Required	Description
`bbox`	No	Bounding box filter
`type`	No
`filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Query' and 'optional filters', but does not disclose return format, whether the query is read-only, or any side effects. This is inadequate for a tool with no structured annotations.

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?

The description is a single concise sentence that states the core purpose without redundancy. It is front-loaded and efficient, though it could be slightly better structured with additional context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters (one nested object, one enum) and no output schema, the description is far too sparse. It fails to explain what the tool returns, how filters behave, or any other contextual details needed by an agent. The tool is more complex than the description acknowledges.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (bbox has a description, type and filter do not). The description adds no additional parameter detail, and the 'filter' parameter remains completely unexplained beyond being an arbitrary object. The description does not compensate for the low schema coverage.

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?

The description clearly states the tool queries Excalidraw elements with optional filters, using a specific verb and resource. It is distinct from sibling tools like get_element (which implies retrieving a single element) or get_selection, though it does not explicitly name them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_element or get_selection. The description only states what the tool does, leaving the agent to infer intended usage based on the name.

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