biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

List verification case records

list_vcr

Lists verification case record metadata—IDs, titles, statuses, and refs—one page at a time, with optional glob and language filters to locate a record before fetching it by ID.

Instructions

Ids, titles, statuses, and refs of verification case records in the configured verification case record 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_vcr tool instead. An optional glob pattern (e.g. 'dead*') filters the listing to the verification case records 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/vcr/ directory (the default behavior, unchanged); any other ISO 639-1-shaped lowercase two-letter code (e.g. 'de') = only that language's docs/vcr/{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

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 substantial work: default page size 25, cap 100, out-of-range values clamped rather than errored, and ValueError behavior for invalid-shaped language or a language lacking a heading-mapping table. It stops short of describing ordering of results or what an empty listing looks like, which is a minor gap rather than a serious one.

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 scope before the parameter detail, and nearly every clause carries operational information. It is a single dense paragraph with nested parentheticals, so it is heavier to parse than it needs to be, but nothing is redundant enough to cut outright.

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, yet the description still names the returned fields, and it fully covers the four undocumented parameters plus the error paths an agent would otherwise hit blind. For a list tool with four optional params and no annotations, nothing needed to call 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 description coverage is 0%, so the description must compensate entirely, and it does: glob gets matching semantics, case-insensitivity, a concrete example ('dead*'), and the None-versus-empty-string behavior; max_results/offset get defaults, a cap, and clamping semantics; language gets its default, shape validation, and exact directory effect. Each parameter's behavior is disambiguated in ways the bare schema could not convey.

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 exact fields returned ('Ids, titles, statuses, and refs of verification case records') and immediately scopes it as paginated context gathering rather than retrieval. It also distinguishes itself from get_vcr by explaining that 'ref' is an opaque identifier to be resolved with that sibling, not a filename.

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 frames the use case ('for context before addressing one by id') and routes the agent to get_vcr for ref-based lookups. It also pre-empts a likely wrong turn by stating there is deliberately no 'all languages' mode, and spells out the glob filter's matching rules including the None vs empty-string distinction.

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

Deploy Server