excalidraw-mcp-obsidian

Overview Schema Source Related Servers Discussions Admin

get_element

Retrieve a specific Excalidraw element by ID from an Obsidian-native .excalidraw.md file, allowing precise modifications without reloading the entire diagram.

Instructions

Get a single Excalidraw element by ID

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": {
      "id": "<id>"
    },
    "name": "get_element"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, but no behavior is disclosed for not-found cases, error handling, permissions, or return format. Minimal transparency beyond the verb itself.

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?

A single six-word sentence, front-loaded with the action verb. No filler or redundant material; every word adds value.

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

Completeness3/5

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

For a simple one-parameter getter, the core purpose is adequately conveyed, but the total absence of annotations and lack of return/error-behavior details leave gaps. It is minimally viable but not fully complete for an agent unfamiliar with MCP conventions.

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?

With 0% schema description coverage, the description compensates by explaining that 'id' identifies the Excalidraw element to retrieve. This adds meaningful semantic context beyond the bare string type, though examples or format expectations are absent.

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?

Crisp verb 'Get' plus specific resource 'single Excalidraw element by ID' clearly states function. The qualifiers 'single' and 'by ID' distinguish it from siblings like query_elements and get_resource.

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 phrase 'by ID' implies this tool is for fetching one known element, providing some implied usage context. However, there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as query_elements for multiple/filtered lookups.

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