biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

List use cases

list_uc

List use case IDs, titles, statuses, and refs from the configured base directory with paging, glob filtering, and optional language selection for context before fetching one 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. The optional language parameter (default 'en') selects the directory scanned: omitted/'en' = the flat docs/uc/ directory (the default behavior, unchanged); any other ISO 639-1-shaped lowercase two-letter code (e.g. 'de') = only that language's docs/uc/{language}/ subdirectory, listing exactly the existing variants of that language (there is deliberately no 'all languages' mode). The language is shape-validated before any file access (an invalid-shaped value is a ValueError, like an invalid id), and a shape-valid language without a packaged heading-mapping table is rejected up front with an actionable ValueError.

Input Schema

Name	Required	Default
`glob`	No
`offset`	No
`language`	No	en
`max_results`	No

Output 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.

Changed1 schema field changedv0.38.0Nov 2, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "title": "Language",
+  "type": "string"
+}

First observedv0.36.0Oct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses paging defaults and cap, clamping rather than erroring on out-of-range values, case-insensitive glob matching, and up-front ValueError behavior for invalid or unsupported language values.

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 dense but front-loaded, starting with the purpose and the ref caveat before covering parameters. It is a single long paragraph with some heavy sentences, but every sentence adds operational meaning and nothing is obviously redundant.

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?

For a four-parameter listing tool with an output schema, the description supplies the missing operational context: ref handling, paging, filtering, language directory selection, and validation failure modes. An agent can call it correctly without opening the schema or making unsafe assumptions.

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 explains all four parameters: glob's case-insensitive matching and null/empty-string semantics, max_results/offset paging defaults and clamping, and language's default, directory selection, and validation behavior.

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 opens with a specific verb and resource: it lists ids, titles, statuses, and refs of use cases from the configured use-case base directory. It explicitly frames the listing as context before addressing an item by id and names get_uc as the follow-up tool, distinguishing it from sibling readers.

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?

It says when to use the tool ('for context before addressing one by id') and routes the opaque ref identifier to get_uc instead of treating it as a filename. The glob, paging, and language behaviors are explained with concrete conditions, including that there is deliberately no 'all languages' mode.

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

Deploy Server