biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

List System Requirements Specifications

list_sysrs

Browse paged System Requirements Specifications with IDs, titles, statuses, and refs; filter by ID pattern and language variant before opening a specific document.

Instructions

Ids, titles, statuses, and refs of System Requirements Specifications in the configured System Requirements Specification 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_sysrs tool instead. An optional glob pattern (e.g. 'dead*') filters the listing to the System Requirements Specifications 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/sysrs/ directory (the default behavior, unchanged); any other ISO 639-1-shaped lowercase two-letter code (e.g. 'de') = only that language's docs/sysrs/{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.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 delivers: paging defaults (25, cap 100), clamping rather than erroring on out-of-range values, glob matching being case-insensitive with None=all and empty=none, and validation ordering for language (shape-checked before file access, rejected if no heading table). This is unusually rich behavioral disclosure.

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-loads what is returned and why, then documents parameters in sequence. It is dense rather than padded, though a few clauses are repetitive (e.g. restating the default/'unchanged' behavior for 'en').

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?

An output schema exists, so return shape needn't be explained; the description covers paging, filtering, language routing, and error conditions for a 4-parameter list tool. Nothing an agent needs to invoke it 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 coverage is 0%, so the description must compensate and does: glob semantics (case-insensitive, default None lists all, empty string matches nothing), max_results/offset paging behavior, and language's default 'en' plus directory-routing and validation rules. Every parameter is given meaning beyond its bare type.

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 (System Requirements Specifications), the fields returned (ids, titles, statuses, refs), and the scope (configured base directory, one page at a time). It also implicitly separates itself from get_sysrs by noting refs are for retrieval 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 a clear when-to-use rationale ('for context before addressing one by id') and routes the agent to get_sysrs for ref-based retrieval. It also clarifies alternatives for language selection (no 'all languages' mode). Lacks an explicit when-not list, but the guidance is strong.

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

Deploy Server