Skip to main content
Glama

List templates

list_templates
Read-onlyIdempotent

List every built-in FlowSimp template. Use it when a starter diagram is a better fit than generating one from text. Takes no arguments. Returns JSON with a templates array of id, label, and editUrl. The ids are swimlane, decision-tree, user-flow, org-chart, flowchart, process, network, mind-map, data-flow, algorithm, bpmn, onboarding, and approval. Each editUrl opens that template in the editor. The list is fixed, and the call does not store or change anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"No arguments."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, yet the description still adds value by specifying the return shape (templates array of id, label, editUrl) and confirming the list is fixed and stores nothing. That return-format disclosure matters because no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and selection guidance are front-loaded, followed by return shape and side-effect guarantees. The 13-id enumeration is lengthy but defensible: the list is fixed, and spelling out the ids lets an agent choose a template without calling the tool.

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?

For a no-argument, read-only listing with no output schema, the description fully covers what is returned, the field names, and the absence of side effects. Nothing needed to call it correctly 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?

Zero-parameter tool, and the description reinforces "Takes no arguments," matching the empty schema. Nothing further is needed.

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?

States a specific verb and resource ("List every built-in FlowSimp template") and scopes it to built-ins, which separates it from the generative sibling create_flowchart. An agent can tell what it returns without opening the 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?

"Use it when a starter diagram is a better fit than generating one from text" gives a clear selection condition against the text-generation path. It stops short of naming create_flowchart or stating when not to call it, but the intent is unambiguous.

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.