biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

List decisions

list_dec

Lists decision IDs, titles, statuses, and refs from the configured decision base directory, with paging, optional glob filtering, and language selection, to find context before fetching one by ID.

Instructions

Ids, titles, statuses, and refs of decisions in the configured decision 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_dec tool instead. The optional language parameter (default 'en') selects the directory scanned: omitted/'en' = the flat docs/dec/ directory (the default behavior, unchanged); any other ISO 639-1-shaped lowercase two-letter code (e.g. 'de') = only that language's docs/dec/{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. An optional glob pattern (e.g. 'dead*') filters the listing to the decisions 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

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.7/5.0

Behavior4/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 validation-ordering (shape-checked before any file access), two distinct ValueError paths including the missing heading-mapping table, clamping rather than erroring on out-of-range paging, and the page-size default and 100 cap. It stops short of describing ordering of results or the response envelope, but the output schema covers the latter.

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 and return fields, and no sentence is filler, but the language clause is a dense multi-clause run-on with nested parentheticals that would read faster as a short bulleted breakdown. Slightly overlong for a four-parameter list tool.

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 read-only listing tool with a rich description and an output schema, nothing an agent needs in order to call it correctly is missing: when to use it, how refs differ from ids, directory scoping, filtering, paging, and failure modes are all present.

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 entirely and it does: `glob` is case-insensitive on id, glob=None lists everything, empty string matches nothing; `language` is an ISO 639-1-shaped lowercase code selecting a directory; `max_results`/`offset` default to 25 and are clamped at 100 rather than errored. Every one of the four parameters gains meaning not present in the bare 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?

Opens with a specific verb and resource plus the returned fields ("Ids, titles, statuses, and refs of decisions in the configured decision base directory") and immediately positions itself against the by-id sibling: "for context before addressing one by id." An agent can distinguish list_dec from get_dec and parse_dec 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?

States the triggering scenario (survey the base before addressing one by id) and routes the 'ref' case explicitly to get_dec. It also sets the boundary conditions for `language` (omitted/'en' = flat docs/dec/, other code = that language's subdirectory), and pre-empts a common wrong assumption by declaring 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