Skip to main content
Glama

list_canvases

Retrieve all canvas files from your Obsidian vault to organize and access visual notes.

Instructions

List all canvas files in the vault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the list_canvases tool, which calls listCanvasFiles from the vault library.
    async () => {
      try {
        const files = await listCanvasFiles(vaultPath);
    
        if (files.length === 0) {
          return { content: [{ type: "text" as const, text: "No canvas files found in the vault." }] };
        }
    
        const formatted = files.map((f, i) => `${i + 1}. ${f}`).join("\n");
        return {
          content: [{ type: "text" as const, text: `Found ${files.length} canvas file(s):\n\n${formatted}` }],
        };
      } catch (err) {
        console.error("Failed to list canvas files:", err);
        return errorResult(`Error listing canvas files: ${err instanceof Error ? err.message : String(err)}`);
      }
    },
  • Registration of the list_canvases tool in the MCP server.
    server.registerTool(
      "list_canvases",
      {
        description: "List all canvas files in the vault",
        inputSchema: {},
      },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose details like pagination, sorting, format of returned data, performance characteristics, or error conditions. The description is too basic for a tool that likely returns multiple items.

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?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list operation with no output schema and no annotations, the description is insufficient. It doesn't explain what data is returned (e.g., file names, metadata, paths), format, or any limitations. Given the complexity of listing files and the lack of structured output documentation, more context is needed.

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 has zero parameters with 100% schema coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for this dimension.

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?

The description clearly states the action ('List') and resource ('all canvas files in the vault'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list_notes' or 'read_canvas', but the specificity of 'canvas files' provides some distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, exclusions, or compare it to similar tools like 'list_notes' or 'search_notes', leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rps321321/obsidian-mcp-pro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server