Skip to main content
Glama

Fluxygram format guide

get_guide
Read-only

Retrieve the Fluxygram diagram guide covering seven diagram types, nodes, edges, steps, captions, motion, live status and storytelling rules. Call it before writing your first diagram.

Instructions

How to write a Fluxygram diagram: the seven diagram types and when to use each, nodes, edges, steps with captions, motion, live status (tracker mode), icons and the storytelling rules. Call it before writing your first diagram.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, non-networked read. The description adds useful substance by disclosing the scope of the reference material, including live status/tracker mode, which hints the guide is a static snapshot rather than live data. It does not say what form the guide comes back in (markdown text, sections, length), which is the main remaining behavioral 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 front-loads the purpose and then packs the topic list densely, and the second is a single actionable call-to-action. Every listed item corresponds to a real content area rather than being decorative.

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 zero-parameter, no-output-schema reference tool, the description covers what is inside the guide and when to call it, which is everything an agent needs to decide to invoke it. The only shortfall is not indicating the volume or format of the returned guide, which would help an agent plan context budget.

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?

The tool takes zero parameters, so the parameter-semantics baseline is 4; there is no argument meaning the description could or should add. Nothing in the description misleads about inputs.

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 states a specific resource -- a how-to guide for writing Fluxygram diagrams -- and enumerates its contents (diagram types, nodes, edges, steps/captions, motion, tracker mode, icons, storytelling rules). It is clearly distinguishable from validate_diagram or get_example by being the rules reference rather than a checker or sample. It does not explicitly name a sibling, which keeps it at 4 rather than 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?

"Call it before writing your first diagram" gives a clear trigger condition for invoking the tool. There is no explicit when-not guidance or named alternative (e.g., 'use get_example for a minimal concrete sample'), so it stops short of the top score.

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