Skip to main content
Glama

List features

list_feat

Lists feature IDs, titles, statuses, and refs from the configured feature base directory, with glob filtering and paging, so you can find the right feature before fetching it by ID.

Instructions

Ids, titles, statuses, and refs of features in the configured feature base directory, one page at a time, for context before addressing one by id. 'ref' is an opaque, extensionless identifier -- not a filename to read from disk -- for documents that have no assigned id; use it with the get_feat tool instead. An optional glob pattern (e.g. 'feat-7*') filters the listing to the features whose id matches it, case-insensitively; glob=None (the default) lists everything, and an empty string matches nothing. max_results/offset control paging (default page size 25, capped at 100); out-of-range values are clamped, not errored. The request path never fully parses a document's body (GitHub issue #187): a folder's row is resolved from its frontmatter+H1 alone until a background warmup (or an on-demand get_feat read) has fully parsed it, so a body-level parse failure may transiently appear healthy, and a missing/wrong-shape H1's error text may transiently differ from get_feat's -- both converge to get_feat's exact error once that file has been fully parsed. Set SPECMGR_FEAT_WARMUP_DISABLED to turn the background warmup off entirely (convergence then depends solely on on-demand reads).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
globNo
offsetNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
offsetYes
resultsYes
truncatedYes
error_countNo
max_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so exceptionally well. It discloses non-obvious behaviors: out-of-range paging values are clamped not errored, case-insensitive glob matching, the request path never fully parses a document body (GitHub issue #187), transient parse inconsistencies that converge over time, and an environment variable to disable warmup. This is rich, implementation-level transparency an agent cannot infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded with purpose, but it becomes lengthy with the warmup/parse convergence caveat spanning multiple clauses. While the information is valuable, the structure could be improved by separating the primary usage from the edge-case transparency, as the current mix of concerns makes it harder to parse quickly.

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?

Despite a rich output schema existing (so return value details aren't needed), the description covers all other essential context: paging, filtering, ref semantics, and the non-trivial caching/parse behavior with environment variable control. For a list tool in a complex system, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates. It explains glob as an optional pattern (with example, case-insensitivity, None vs empty string behavior), and defines max_results/offset as paging controls with default page size 25 and a cap of 100, plus clamping of out-of-range values. Every parameter gets meaningful semantic detail absent from the schema.

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 (list) and resource (features), names the exact fields returned ('Ids, titles, statuses, and refs'), and gives the location (configured feature base directory). It also distinguishes itself from get_feat by explaining the 'ref' handling and routing to get_feat for addressing by id, making it clearly differentiable from its siblings.

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 states the purpose is 'for context before addressing one by id' and directs to 'get_feat' for retrieving a document once its ref is known. It also clarifies glob semantics (None vs empty string) and paging defaults, leaving no ambiguity about when and how to use the tool versus alternatives.

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