Skip to main content
Glama

get_canvas

Read-onlyIdempotent

Obtiene un canvas con su contenido completo (JSON de nodos y edges del diagrama). El campo 'content' es el estado serializado del whiteboard.

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": {
      "canvas_id": "<canvas_id>"
    },
    "name": "get_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvas_idYesID del canvas
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so the safety profile is covered. The description adds behavior beyond that by explaining the shape of the returned payload ('content' = serialized whiteboard state with nodes/edges), which matters because there is no output schema. It does not cover error/not-found behavior, so not a 5.

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 short sentences with no filler, leading with the operation and following with the one piece of payload clarification an agent needs. Nothing is restated or redundant.

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 simple two-parameter read with full schema coverage, complete annotations and no output schema, the description supplies the one missing piece (what 'content' contains). Minor gaps remain around missing-canvas behavior, but nothing essential for correct invocation is absent.

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 the schema already explains both canvas_id and workspace_id (including that omitting workspace_id searches all workspaces). The description adds no syntax, format, or scoping detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Obtiene un canvas') plus the scope of what is returned ('contenido completo ... JSON de nodos y edges'). It is clearly distinguishable from list-style siblings such as get_canvases, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by 'contenido completo': this is the single-canvas fetch when you need the diagram body, not a listing. There is no explicit when-to-use/when-not statement and no named alternative (e.g. get_canvases for enumeration), so the agent must infer the routing.

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