Local DevLog MCP

Overview Schema Source Related Servers Discussions Admin

List daily drafts

list_daily_drafts

Read-only

Retrieve daily draft versions with optional filters for work date, timezone, or approval status to manage review workflows. Use filters to focus on pending, approved, or rejected drafts.

Instructions

List current daily draft versions, optionally filtered by date, timezone, or status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_daily_drafts"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No
`timezone`	No
`workDate`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`drafts`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.5.0Oct 26, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / drafts / items / properties / approvedAt / anyOf

Previous value: -[
-  {
-    "format": "date-time",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / drafts / items / properties / approvedVersion / anyOf

Previous value: -[
-  {
-    "exclusiveMinimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / drafts / items / properties / createdAt / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

addedOutput schema / properties / drafts / items / properties / draftId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedOutput schema / properties / drafts / items / properties / updatedAt / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

addedOutput schema / properties / drafts / items / properties / version / maximum
```
Added value: +9007199254740991
```

First observedv0.4.1Oct 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint already declares this is a safe read, so the description's burden is lower. It adds that filters are optional and that results are 'current' drafts, but discloses nothing about ordering, pagination, or how drafts are scoped. Adequate but with clear gaps.

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?

A single front-loaded sentence with no filler. Efficient and clear, though it leaves no room for the contextual detail the tool arguably needs.

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?

An output schema exists so return values need not be explained, and the read-only annotation covers the safety profile. For a simple filtered-list tool, the description is nearly complete, missing only ordering/scope detail.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It names date, timezone, and status filters, mapping roughly to workDate, timezone, and status, but adds no format details (e.g., date syntax, timezone format) beyond the field names already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and resource (current daily draft versions), making clear it returns multiple drafts, which distinguishes it from get_daily_draft. It does not explicitly name siblings or note the scope limitation beyond 'current', so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'optionally' implies filters are non-mandatory, but there is no explicit guidance on when to use this versus get_daily_draft or get_daily_activity, nor any exclusions. Usage is only implied from the resource name.

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

Deploy Server