Skip to main content
Glama
Sign In
excalidraw-mcp-obsidian

excalidraw-mcp-obsidian

by zzmkxd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_resource

Retrieve Excalidraw resources such as scene, library, theme, or elements for use in Obsidian-native diagrams.

Instructions

Get an Excalidraw resource

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": {
      "resource": "<resource>"
    },
    "name": "get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations are absent, so the description carries the full burden of disclosing behavior. It only says 'Get' with no mention of read-only semantics, side effects, return format, or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only a single sentence, but this brevity reflects under-specification rather than conciseness. It contains zero useful information beyond what the tool name already conveys.

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

Completeness1/5

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

For a tool with no annotations and no output schema, the description is critically incomplete. It omits resource types, return values, example usage, and any distinguishing context, leaving the agent to guess the tool's function.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain the 'resource' parameter. While the schema provides an enum, the description adds no meaning about what each resource type represents or how to use them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get an Excalidraw resource' essentially restates the tool name without adding specificity. It does not enumerate the supported resource types (scene, library, theme, elements) nor differentiate from similarly named siblings like get_element or get_selection.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. Sibling tools like get_element, get_selection, and export_scene clearly overlap, yet the description offers no context or exclusions.

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