biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

Create task list

create_tsk

Creates a validated task-list document, assigns a fresh ID, derives the filename from its H1 title, and writes it to the task-list directory; also creates translation variants for existing lists.

Instructions

Create a new task list: assigns a fresh id, derives a filename from the body's H1 title, validates the submitted body-only content, and writes the new document to the task list base directory. A content-validation failure of the submitted body returns a non-raising ValidateResult (valid=False, a single errors[].message capped at 300 chars as the generic validate tool caps it, feat-110) instead of raising AssertionError/pydantic.ValidationError (ADR f14f125e-eaad-4f4f-a6fd-3c931bed726e, GitHub issue #204 -- case 5 of the ADR 519d1206 non-raising-structured-result workaround chain); nothing is written in that case. The structure reference is the get_tsk_schema tool (the generated JSON Schema); the get_tsk_template/get_tsk_example tools return the authoring template and a complete sample. Returns the newly created document's frontmatter only (no body); use the corresponding get_tsk tool to fetch the full document afterward. The optional language parameter (default 'en', feat-197-i18n) selects the language to create the document in: omitted/'en' = a new flat docs/tsk/ document with a fresh id, exactly the default behavior (id must then be omitted); a non-default ISO 639-1-shaped lowercase two-letter code (e.g. 'de') creates a TRANSLATION of an existing task list instead: id -- the shared id of the existing EN source document -- is then required (no fresh id is assigned; the variant carries the same id), the EN source must exist (else TskNotFoundError), and the variant is written to docs/tsk/{language}/ under the EN source's exact file name with status draft; content is validated through that language's heading-mapping table (translated headings are accepted) and persisted verbatim. An existing variant of that id and language is never overwritten (FileExistsError). A malformed language, one with no packaged heading-mapping table, a missing id for a non-default language, or an id given for the default language is a ValueError raised before any file access.

Input Schema

Name	Required	Default
`id`	No
`content`	Yes
`language`	No	en

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.38.0Nov 2, 2026

addedInput schema / properties / id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Id"
+}

addedInput schema / properties / language

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

Changed1 schema field changedv0.37.0Oct 24, 2026
- addedOutput schema / $defs / TskFrontmatter / properties / status / enum
```
Added value: +[
+  "active",
+  "cancelled",
+  "done",
+  "draft"
+]
```
First observedv0.36.0Oct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so thoroughly: validation failures return a non-raising ValidateResult with nothing written, only frontmatter is returned, translation variants are never overwritten, and TskNotFoundError/FileExistsError/ValueError cases are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and most of the content is relevant, but the single dense paragraph contains internal traceability noise such as long ADR UUIDs, issue #204, and feat tags. The complexity justifies substantial length, but tighter structure and removal of internal references would improve scanability.

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?

Given the lack of annotations, three parameters, translation-mode branching, and an existing output schema, the description covers creation, validation, persistence location, return shape, and error outcomes. No material invocation detail appears to be 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?

With schema description coverage at 0%, the description fully compensates by defining all three parameters: content is body-only validated content with an H1-derived filename; id is optional for default creation but required as the shared source id for translations; language defaults to 'en' and selects translation behavior with heading mapping.

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 'Create a new task list' and specifies id assignment, filename derivation from the body's H1 title, body validation, and writing to the task list base directory. The resource is unambiguous against sibling create tools such as create_prb and create_req.

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 routes structure consultation to get_tsk_schema/get_tsk_template/get_tsk_example and full document retrieval to get_tsk. It also distinguishes default creation (language omitted or 'en', id omitted) from translation mode (non-default language, existing id required) and describes the error conditions that select each path.

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

Deploy Server