biz.dfch.SpecMgr

Overview Schema Source Related Servers Discussions Admin

Create task list

create_tsk

Create a validated task list document with a fresh ID and H1-derived filename, then write it to the task list directory. Returns frontmatter only.

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. Returns the newly created document's frontmatter only (no body); use the corresponding get_tsk tool to fetch the full document afterward.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.0Oct 17, 2026

TDQS

A3.9/5.0

Behavior4/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 it does well: it discloses that invalid content returns a non-raising ValidateResult with a 300-char cap on error messages, that nothing is written in that case, and that only frontmatter is returned. It does not cover permissions, overwrite behavior, or id-collision handling.

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

Conciseness2/5

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

A single very long run-on sentence packed with internal ADR hashes (f14f125e...), a GitHub issue number, and a feat-110 tag. The routing guidance ('use get_tsk') is buried at the end, and the traceability jargon is not actionable for an agent selecting or invoking the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single required param, no annotations, and an existing output schema, the description covers the essential operational facts: validation behavior, what is returned, and the follow-up tool. An output schema existing means return values need not be explained, which the description respects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (content) with 0% schema description coverage. The description clarifies that content is 'body-only' and validated, and that the H1 title drives the filename, which adds real meaning beyond the bare schema. But it doesn't specify accepted formats or validation rules that the agent could anticipate.

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 and resource (create a new task list) and enumerates concrete sub-steps: fresh id assignment, filename derivation from the body's H1, content validation, and document write. This clearly distinguishes create_tsk from the many sibling get_/list_/parse_/create_ tools across other artifact types.

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?

Explicitly tells the agent to use get_tsk afterward to fetch the full document, since only frontmatter is returned. However, it gives no guidance on when to prefer create_tsk over create_* siblings for other artifact types, or any preconditions (e.g., where the body must come from).

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

Deploy Server