Skip to main content
Glama

list_canvases

Lists the canvases in your Studiolo projects and shows how many items each canvas contains, so you can review deliberate compositions rather than folders.

Instructions

List the canvases in the person's Studiolo projects, with how many items each holds.

A canvas is a composition — things they deliberately put next to each other — which is a different thing from a folder, where items merely share a category. Reviewing a canvas is therefore a much more pointed question than reviewing the archive.

Canvases live in the canvas app's browser storage and are mirrored to disk on every change, so what is reported here is the state as of the last edit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real context: canvases live in the canvas app's browser storage, are mirrored to disk on every change, and reported state is 'as of the last edit.' That staleness caveat is genuinely useful. However, it says nothing about ordering, pagination, or what an empty result looks like for a list operation.

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?

Three sentences, front-loaded with the action and the return payload before the conceptual definition. The middle sentence is slightly discursive ('which is a different thing from a folder, where items merely share a category'), but it earns its place by establishing the sibling distinction.

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 no-parameter list tool with no output schema, the description covers what is returned (canvases plus item counts), data freshness, and the conceptual distinction from folders. Missing only minor details like result ordering and behavior on an empty project.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The text does confirm implicitly that the listing is unscoped apart from 'the person's Studiolo projects.'

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 first sentence names a specific verb and resource ('List the canvases in the person's Studiolo projects') and adds the returned payload ('with how many items each holds'). The second sentence defines what a canvas is and explicitly contrasts it with a folder, which is the key sibling distinction (list_folders).

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?

The description gives a clear selection rule: canvases are deliberate compositions, folders are mere category groupings, and 'reviewing a canvas is therefore a much more pointed question than reviewing the archive.' That tells the agent when this tool is the sharper choice, though it never states exclusions or prerequisites explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.