Skip to main content
Glama
mermaidonline-mcp

mermaidonline-mcp

by j-river

Recover Mermaid source from a share link

decode_mermaid_share
Read-onlyIdempotent

Recover Mermaid source from a pako:/base64: share token, fragment, or HTTP(S) URL without fetching it; optionally preserve extension state as untrusted JSON.

Instructions

Recover Mermaid source from a supported pako:/base64: share token, fragment or HTTP(S) URL without fetching it. Whole-state mode preserves extension fields as untrusted JSON. Unsupported formats and oversized expansion are rejected. No syntax validation or rendering.

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": {
      "share": "<share>"
    },
    "name": "decode_mermaid_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
shareYespako:/base64: token, fragment or HTTP(S) URL. Parsed locally, never fetched.
includeStateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotency and closed-world safety, so the bar is lower, yet the description adds real behavior: local parsing with no network fetch, rejection of unsupported formats, an oversized-expansion guard, and that whole-state mode retains extension fields as untrusted JSON. It lacks detail on error signal shape but goes well beyond the annotations.

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?

Four tight sentences, front-loaded with purpose, then input forms, then mode behavior, then limits. Every sentence carries information an agent needs; there is no filler.

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?

There is no output schema, and the description never states what the return value looks like (plain Mermaid string vs structured whole-state object), which matters given the includeState mode. Everything else an agent needs to invoke it safely is present.

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?

The share parameter is well documented in the schema, but includeState has only a default and no schema description (50% coverage). "Whole-state mode preserves extension fields" partially compensates by explaining what that flag does, but not precisely enough to fully cover the gap (e.g., what exactly is returned differently).

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?

The description uses a specific verb ("Recover") on a specific resource ("Mermaid source") and names the accepted input forms (pako:/base64: token, fragment, HTTP(S) URL). It is clearly the inverse of encode_mermaid_share, but it never names that sibling, so differentiation is implied 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 Guidelines3/5

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

It makes the scope clear ("without fetching it", "No syntax validation or rendering"), which implicitly tells the agent when the tool is appropriate. However, it gives no explicit when-to-use versus encode_mermaid_share guidance and no prerequisites for what counts as a "supported" token.

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