Skip to main content
Glama
Sign In
diag-weaver

diag-weaver

by wldxiaobai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

editor_ensure

Open the local draw.io canvas in the browser and wait until it connects, ensuring the editor is ready for diagram edits.

Instructions

Open the local draw.io canvas in the browser if needed and wait until it is connected. Does not create store directories.

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": "editor_ensure"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations to fall back on, the description discloses meaningful behavior: it may open a browser, it blocks/waits for a connection, and it does not create store directories. However, it omits details such as timeout behavior, side effects of launching a browser, or what 'connected' means, so transparency is only partial.

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?

One sentence with an active verb, immediately states the action and wait condition, plus a useful explicit non-effect. No filler or redundancy.

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

Completeness4/5

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

For a zero-parameter setup tool, the description covers what the tool does, the environment it affects, and an explicit non-effect. It lacks timeout/failure details, but the schema and parameter surface are minimal, so this is reasonably 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?

The tool has zero parameters and schema coverage is complete, so the baseline of 4 applies. The description does not need to explain parameters.

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 clearly states a specific action ('Open the local draw.io canvas') and an outcome ('wait until it is connected'), which is distinct from all sibling diagram_* tools that perform modifications or reads on diagrams. The negative claim 'does not create store directories' also helps disambiguate scope.

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?

While 'if needed' implies this is a setup or prerequisite step, the description provides no explicit guidance about when to call this tool versus alternatives, nor any conditions under which it should be skipped.

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