Skip to main content
Glama
Sign In
Draw.io MCP Server

Draw.io MCP Server

by Geoffrey-Fang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_colors

Manage and apply custom color schemes and palettes to diagrams, including setting, retrieving, applying, and resetting colors.

Instructions

管理图表的颜色方案和调色板

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": {
      "diagram_id": "<diagram_id>",
      "action": "<action>"
    },
    "name": "manage_colors"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes颜色管理操作
paletteNo调色板定义
diagram_idYes图表ID
color_mappingNo颜色映射规则

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

There are no annotations, so the description carries full responsibility for disclosing behavior. It only says 'manage color schemes and palettes', giving no information about side effects, whether operations are read-only or mutating, or what happens to existing colors.

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 a single short sentence but it is under-specified rather than concise. It lacks actionable detail, so it does not earn its place as a useful descriptor.

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?

With no annotations, no output schema, and a complex 4-parameter input (including nested objects), the description is far from complete. It does not explain the actions, their effects, or expected return values.

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

Parameters3/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. The description adds no additional meaning to the parameters; all semantics must come from the schema, which is adequate.

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 uses the generic verb 'manage' (管理), which does not specify the concrete operations available (set, get, apply, reset). It does not distinguish this tool from overlapping siblings like apply_theme or update_style.

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 apply_theme or update_style. The description gives no context about the intended scenarios 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