biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

List use cases

list_uc

Lists use cases with IDs, titles, statuses, and refs from the configured use-case directory, one page at a time, with optional glob filtering and paging to gather context before addressing by ID.

Instructions

Ids, titles, statuses, and refs of use cases in the configured use-case 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_uc tool instead. An optional glob pattern (e.g. 'dead*') filters the listing to the use cases 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`glob`	No
`offset`	No
`max_results`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`offset`	Yes
`results`	Yes
`truncated`	Yes
`error_count`	No
`max_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.0Oct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses paging defaults (25, capped at 100), that out-of-range values are clamped rather than errored, glob matching is case-insensitive, glob=None lists everything while an empty string matches nothing, and that 'ref' is an opaque extensionless identifier rather than a disk filename.

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 the returned fields and scope, and every clause carries information. It is a dense, run-on single paragraph, however, which makes the glob and paging rules harder to scan than they need to be.

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 an output schema existing (so return values need not be explained), the description still summarizes the returned fields, and it fully covers filtering, paging, and identifier semantics. Nothing an agent needs to call this list tool correctly is missing.

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%, so the description must compensate, and it does: glob semantics (case-insensitive, None vs empty string), and max_results/offset paging behavior with defaults and caps are all explained. Each of the three parameters gains meaning not present in 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 and resource ('list use cases in the configured use-case base directory') and enumerates exactly what is returned (ids, titles, statuses, refs). It also differentiates itself from the get_uc sibling by framing the listing as context 'before addressing one by id'.

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?

Gives clear usage context ('for context before addressing one by id') and routes the agent to the alternative for retrieval: use the 'ref' with get_uc instead. It does not state explicit when-not conditions (e.g., when to prefer a targeted lookup over listing), but the alternative is named.

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

Deploy Server