Skip to main content
Glama

list_folders

Lists library folders with item and labeled-item counts, including nested roots, so you can see which folders are searchable by meaning and which only by filename.

Instructions

List the folders the library reads, with their item counts and how many items in each carry a written label.

The archive may span more than one root folder on disk — each is listed with its own folders nested under it, and a folder is named "@/" so the two can be told apart. Passing just the folder name to search_inspo or recent_inspo matches that folder in any root.

The labeled count is the useful number: it says where the archive can be searched by meaning and where it can only be searched by filename. A folder showing "0 labeled" holds material that text search effectively cannot reach.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that the archive may span multiple roots, explains the '@<root>/<folder>' naming, and clarifies what the labeled count means. It does not mention permissions, rate limits, or whether the operation is strictly read-only, but 'List' and 'reads' strongly imply a safe read 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?

The description is front-loaded with the core purpose and then explains the multi-root naming and labeled-count interpretation. It is somewhat long, but each paragraph adds actionable meaning for an agent, with little wasted wording.

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?

There is no output schema, so the description must explain the return shape, and it does: folders, item counts, labeled counts, multi-root nesting, and naming. It also explains how to use the returned folder names with sibling search tools, making the definition complete for a zero-parameter listing tool.

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, so the baseline is 4. The description adds useful context about how folder names are formed and consumed by sibling tools, but there are no parameters whose semantics need further explanation.

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 and resource: it lists folders the library reads, including item counts and labeled counts. It also distinguishes the multi-root naming convention and explains how folder names relate to search_inspo and recent_inspo, so an agent can identify the tool's role without opening the schema.

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 clear usage context: use the listed folder names with search_inspo or recent_inspo, and interpret the labeled count to know where meaning-based search is possible. It does not explicitly state when not to use this tool versus list_canvases or other siblings, so it falls short of full alternative routing.

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