Skip to main content
Glama

List the folder's documents

folio_documents
Read-onlyIdempotent

List all Markdown and diagram documents in a folder with their declared kind, so you can see what exists or filter by document type.

Instructions

List every markdown and diagram document under a folder of the served folder, with the kind a FOLIO.md declaration gives it. Use it to see what exists or which documents are of a kind; for documents matching a condition - a title, a field's value, a link - query folio.documents or kind. with folio_query, and for one document's blocks use folio_document. Answers {ready, documents: [{path, kind}]}: kind is null where no declaration places the document; ready false means Folio is still reading the folder and the list is incomplete, so ask again shortly. A list cut to fit one answer adds omitted, the entries each list left out, and narrow, how to ask for less.

Input Schema

NameRequiredDescriptionDefault
folderNoA folder, relative to the served folder or absolute under it, such as notes/; omit for the whole folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), and the description adds context they cannot: 'ready: false' means the folder is still being read so the list is incomplete and should be re-asked, 'kind' is null when no declaration places a document, and truncated results carry 'omitted' and 'narrow'. These are non-obvious traits an agent would otherwise misread.

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?

Front-loaded with purpose, then routing alternatives, then return semantics; no filler sentences. It is dense and near the upper length limit for a one-parameter list tool, but each clause carries distinct information.

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, and the description compensates by documenting the response shape ({ready, documents: [{path, kind}]}) plus the truncation fields. Combined with the sibling routing, an agent has everything needed to call it and interpret the result correctly.

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 coverage is 100% and the single optional parameter 'folder' is fully documented there, including relative-path syntax and the omit-for-root behavior. The description only echoes the folder scoping concept without adding format or semantics beyond the schema, so the baseline 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?

States a specific verb and resource: 'List every markdown and diagram document under a folder', and immediately contrasts with folio_query (filtered queries) and folio_document (single document's blocks). An agent can distinguish it from all siblings without opening a 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?

Explicitly says when to use it ('see what exists or which documents are of a kind') and when not to, naming the alternatives folio_query / kind.<name> and folio_document for the other cases. This is the exact when/when-not/alternatives pattern.

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