Skip to main content
Glama

Read the declared kinds and rules

folio_kinds
Read-onlyIdempotent

Read the FOLIO.md declarations applying at a path: document kinds with their fields, rules every row must satisfy, and health entries. Use it before writing a document to learn its fields and rules.

Instructions

Read what the FOLIO.md declarations applying at a path declare: the kinds of documents with the fields each carries, the rules - queries whose every row is a violation - and the health entries, layered from the served folder down as Folio applies them. Use it before writing a document of a kind, to learn its fields and the rules it must keep; for one document's own kind and field values use folio_document, and for the rules broken now folio_health. Answers {declarations: [FOLIO.md paths, outermost first], kinds: [{name, declaredIn, where, fields}], rules: [{name, declaredIn, query, message, severity, line and block: where it is declared}], health: [{declaredIn, where, skip, error}]}, every list empty where nothing is declared. 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
pathNoA document, relative to the served folder or absolute under it, such as notes/plan.md, or a folder ending in /, such as notes/; omit for the served folder itself

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not needed for the safety profile, but it adds real substance: layering semantics ('from the served folder down as Folio applies them'), empty-list semantics, and truncation signals (omitted, narrow). It does not say what happens on an invalid or non-existent path, which is the remaining behavioral gap.

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?

Purpose and usage are front-loaded, then return shape, then truncation - a logical order with no filler sentences. The second sentence is long and clause-heavy, which slows scanning slightly, but every clause carries 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 fully by spelling out the return object field-by-field (declarations, kinds, rules, health) and the truncation contract. Combined with the usage routing, an agent has everything needed to call it and interpret the result.

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?

Schema coverage is 100% and the path parameter is already documented with relative/absolute and file-vs-folder examples, so the baseline is 3. The description adds resolution meaning beyond the schema by framing the result as declarations 'layered from the served folder down', clarifying that the path only scopes which layer 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: read the FOLIO.md declarations applying at a path, enumerating the three payload categories (kinds, rules, health) and the layering order. It explicitly distinguishes itself from siblings folio_document and folio_health, so an agent can route without opening any 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?

Gives an explicit when-to-use ('before writing a document of a kind, to learn its fields and the rules it must keep') and names the two alternatives with the conditions that select them: folio_document for a single document's own kind and values, folio_health for currently-broken rules.

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