Skip to main content
Glama

Check Mind Map Readiness

flowzap_mindmap_approve
Read-onlyIdempotent

Check if valid FlowZap Code is suitable for Mind Map rendering. Returns structured verdict with errors (blocking), warnings (advisory), and info. Rules: diamonds and taskboxes are ERROR (not rendered in mind maps), multiple circles produce WARNING (only the first is the root), edge directions are INFO (ignored by renderer), large/deep diagrams produce advisory warnings. Uses local parsing only - no API call.

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": {
      "code": "<code>"
    },
    "name": "flowzap_mindmap_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesFlowZap Code to inspect for mind map readiness

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive), the description discloses that parsing is local with no API call and that results are a structured verdict split into errors, warnings, and info. It goes further by enumerating the specific rule set (diamonds/taskboxes are ERROR, multiple circles WARNING, edge directions INFO, size/depth advisories), which is exactly the behavioral detail an agent needs.

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?

The verdict shape and the no-API-call fact are front-loaded, and the rule enumeration is compressed into a compact clause list with no filler. Every sentence carries information an agent would otherwise have to guess.

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

Completeness5/5

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

With one simple parameter, no output schema, and only read-only annotations, the description still describes the return structure (errors/warnings/info verdict) and the exact conditions that trigger each severity. Nothing needed to call or interpret this tool is missing.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is already high. The description adds meaning by implying the input must be valid FlowZap Code, giving the agent a precondition the schema alone does not convey.

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 first sentence gives a specific verb and resource: check whether FlowZap Code is suitable for Mind Map rendering, which is clearly distinct from syntax validation done by flowzap_validate. It does not explicitly name the sibling tools it differs from (flowzap_mindmap_validate, flowzap_validate), so it stops short of a 5.

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 phrase 'if valid FlowZap Code' establishes a prerequisite (run validation first) and the framing makes clear this is a pre-render readiness check rather than a mutation or fetch. No explicit when-not or named-alternative routing is given, so it is clear context without full exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.