Skip to main content
Glama

Generate a wall canvas

generate_canvas

THE TOOL FOR ANY CANVAS. Generate the large-format WALL CANVAS for ONE activity using Metodic's real canvas generator, and return it as a branded document in the chat (also saved to the session, and replayable 1:1 to a Miro board). This is the big thing that goes ON THE WALL and that a group fills in together — sized to who shares it (one A1 for the whole room, an A2 per small group) — as opposed to generate_worksheet, which makes the A4 that each participant works on alone. Ask for this whenever the user says canvas, wall canvas, poster, large format, brownpaper, matrix or mapping wall. Give the activity's number (1-based, from the agenda). Takes ~20-30s and 0.5 Metodic credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoPrint size. Leave it on auto: the canvas is A1 when the whole room shares it and A2 when each small group gets its own. Only set it when the user asks for a size.
activityYes1-based activity number from the agenda.
regenerateNoOnly set this to true when the user explicitly wants a NEW version. Left out, an existing one is returned as-is and costs nothing.
session_idYesThe Metodic session id.
canvas_typeNoOptional canvas shape. Metodic has ready-made ones: swot, empathy-map, stakeholder-map, business-canvas, priority-matrix, decision-matrix, journey-map, reflection. Anything else (or leaving it out) makes Metodic design a canvas around the method itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description goes beyond them by disclosing the return form (branded document in chat, saved to session, replayable 1:1 to Miro), the runtime (~20-30s), the cost (0.5 credit), and the regenerate/caching behavior. It does not explain what regeneration replaces, but the added context is substantial.

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?

Front-loaded with the core purpose and sibling contrast, then trigger phrases and cost. It is on the long side with heavy capitalization for emphasis, but nearly every sentence carries routing or behavioral information.

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 no output schema, the description covers what an agent needs: what is produced, where it goes, cost, timing, sizing defaults, and the sibling it must not be confused with. Nothing material for correct invocation is missing.

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 coverage is 100%, so the schema already documents all five parameters including the enum default logic and the regenerate caveat. The description only restates the 1-based activity number and the auto-sizing rationale, adding no new syntax or format detail beyond the schema.

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 (generate the large-format wall canvas for one activity) and explicitly distinguishes itself from the sibling generate_worksheet by contrasting wall-fills-in-together vs A4-individual. An agent can route canvas vs worksheet requests 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger phrases (canvas, wall canvas, poster, large format, brownpaper, matrix, mapping wall), names the alternative (generate_worksheet) and the condition that separates them, and states the required input (activity number from the agenda).

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.

Resources