Skip to main content
Glama

get_supported_diagrams

Discover supported Mermaid.js diagram types, keywords, aliases, and categories; filter by query or category to find the right syntax guide.

Instructions

Returns the Mermaid.js engine version (v12.3.0) and the full catalog of all 37+ supported diagram types, keywords, aliases, and categories. Pointers guide the AI to query get_diagram_syntax_guide for deep syntax rules.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search query to match against diagram names, keywords, aliases, or descriptions
categoryNoOptional category filter: "uml", "architecture", "planning", "charts", or "grammar"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it does so reasonably by framing the tool as a read-only lookup and disclosing the pinned engine version and the ~37+ entry catalog, plus where to go next. It is silent on whether the catalog is a static snapshot versus live, how large the payload is, and whether query and category filters combine.

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?

Two sentences, zero filler, and the highest-value fact (what is returned, including the version) comes first while the sibling hand-off comes second. Every clause earns its place.

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-optional-parameter read tool with no output schema, the description does the essential work: it says what comes back and where the agent should go for syntax detail. The one real gap is that it advertises the 'full catalog' without noting that the query and category parameters narrow that result, which could mislead an agent about what it receives.

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 schema already fully documents the optional query and category parameters, making 3 the correct baseline. The description only faintly echoes them by mentioning 'keywords, aliases, and categories' as catalog content, and never explains that these two parameters filter the returned catalog.

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 opens with a specific verb and resource: it 'Returns the Mermaid.js engine version (v12.3.0) and the full catalog of all 37+ supported diagram types.' It also separates itself from the sibling by naming get_diagram_syntax_guide as the deep-syntax counterpart, so an agent can route between the two without opening either schema.

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 second sentence establishes a clear division of labor: this tool is the catalog/version index, while get_diagram_syntax_guide holds deep syntax rules. That gives the agent an implicit when-to-use split, but there is no explicit trigger such as 'call this before rendering' nor any stated when-not-to-use condition.

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