Skip to main content
Glama

get_canvases

Read-onlyIdempotent

Lista los canvases del workspace (whiteboard/diagrama visual). Retorna metadata sin el contenido del canvas. Para ver el contenido completo de un canvas: usar get_canvas(canvas_id).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
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
parent_document_idNoFiltrar por documento padre

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior are covered. The description adds a non-obvious behavioral fact beyond them: the result is metadata only and deliberately excludes canvas content, which prevents an agent from mis-expecting payload data. It does not mention result volume or pagination, which keeps it below 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?

Three short sentences, each doing distinct work: what it lists, what it returns, and where to go instead. The purpose and the content-scope caveat are front-loaded, and there is no filler or repetition of the title.

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 three-parameter read-only list tool with full schema coverage and rich annotations, the description covers purpose, return scope and sibling routing, which is essentially everything an agent needs to call it correctly. The only omission is any hint about result volume or pagination, which the schema's limit parameter largely absorbs.

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 all three parameters in detail, including the important rule that omitting workspace_id searches all of the person's workspaces in a single call. The description adds no parameter-level meaning of its own, so the baseline of 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 uses a specific verb ("Lista") with a specific resource ("canvases del workspace") and even disambiguates the resource for an agent that doesn't know the domain ("whiteboard/diagrama visual"). It explicitly contrasts itself with the sibling get_canvas, so an agent can choose between them 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?

It states exactly when to use the alternative: "Para ver el contenido completo de un canvas: usar get_canvas(canvas_id)." That single sentence establishes both the when-to-use-this (browse/list) and when-to-use-the-other (need full content) conditions, which is precisely the routing information an agent needs.

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