Skip to main content
Glama

Generate Mind Map Skeleton

flowzap_mindmap_template
Read-onlyIdempotent

Generate a ready-to-extend FlowZap Code skeleton for a Mind Map. Returns a tree structure with a central circle root, rectangle branches and sub-branches, and optional cross-links between branches. Use this to bootstrap a new mind map.

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

Input Schema

NameRequiredDescriptionDefault
depthNoDepth of sub-branches per main branch (default: 2, max: 4)
topicNoCentral topic label for the mind map root (default: 'Central Topic')
branchesNoNumber of main branches from the root (default: 3, max: 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful value beyond that by describing the shape of what comes back — a tree with a central circle root, rectangle branches/sub-branches, and optional cross-links — which tells the agent what 'skeleton' concretely means. It does not clarify whether the result is a string of FlowZap Code or a structured object, a minor remaining gap.

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: the first states the action and the artifact, the second describes the returned structure, the third gives the use case. The most decision-relevant information (what it creates) is front-loaded.

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?

With no output schema and zero required parameters, the description carries the load of explaining the return value, and it does so with specific structural detail (root circle, rectangle branches, cross-links). What remains thin is the relationship to the rest of the mind-map tool family and the exact output format (code text versus object).

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% and each parameter (depth, topic, branches) has its own description with defaults and maximums, so the description need not repeat them. It adds no meaning beyond the schema — it never mentions that depth and branches control the size of the generated tree, which would have been a cheap, helpful clarification. Baseline 3 applies.

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 names a specific verb and resource ('Generate a ready-to-extend FlowZap Code skeleton for a Mind Map') and immediately describes the artifact produced (tree with circle root, rectangle branches, optional cross-links). This clearly separates it from siblings like flowzap_mindmap_validate, flowzap_mindmap_approve, and flowzap_mindmap_create_playground, which operate on an existing map rather than bootstrapping a new one.

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 closing sentence 'Use this to bootstrap a new mind map' gives an explicit when-to-use context, and the word 'skeleton' implies it is a starting point rather than a finished artifact. It stops short of naming exclusions or the follow-on tools (validate/approve/playground), so the agent must infer the rest of the workflow.

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.