Skip to main content
Glama
cloudsketch-mcp

cloudsketch-mcp

Official

Open Mermaid in CloudSketch AI

open_in_cloudsketch
Read-only

Create a link that opens any Mermaid diagram in the CloudSketch AI editor for restyling or export to PowerPoint, Word, PNG, SVG, PDF, or draw.io; no account or upload required.

Instructions

Make a link that opens any Mermaid diagram in the CloudSketch AI editor, to restyle it or export it to PowerPoint, Word, PNG, SVG, PDF or draw.io. Needs no account and uses no credits; the diagram travels inside the link and is not uploaded.

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": {
      "mermaid": "<mermaid>"
    },
    "name": "open_in_cloudsketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional title.
mermaidYesThe Mermaid source code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds real behavioral facts beyond them — no account required, no credits consumed, and the diagram is carried inside the link rather than uploaded. That privacy/cost disclosure is exactly the kind of context annotations cannot carry. It stops short of stating the exact return value or any size limits on the payload.

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?

Purpose is front-loaded in the first clause, then benefits and constraints follow — no filler sentences. The format list (PowerPoint, Word, PNG, SVG, PDF, draw.io) makes the second half slightly run-on, but every element is informative.

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 two-parameter, read-only, no-output-schema tool, the description covers what it does, why you'd use it, and its cost/auth/privacy traits. Only minor gaps remain: the concrete return shape (a URL string) and any limits on the embedded diagram.

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 coverage is 100%, with both `mermaid` (required) and optional `title` documented in the schema. The description adds no parameter-level detail (e.g., whether `title` labels the link or the diagram in the editor), so the baseline 3 applies.

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?

"Make a link that opens any Mermaid diagram in the CloudSketch AI editor" gives a concrete verb (make a link) and a concrete resource (Mermaid source rendered in an external editor). This is plainly distinct from the generate_* siblings, but the description never names or contrasts them, so sibling differentiation is left implicit rather than stated.

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

Usage Guidelines4/5

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

The intent is clear: use it when you want to "restyle" a diagram or "export it to PowerPoint, Word, PNG, SVG, PDF or draw.io." That is meaningful use context, but there is no explicit when-not guidance and no named alternative for agents that actually want to create a diagram from scratch.

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