things3-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_completed

Sync completed tasks to other systems by retrieving to-dos finished within a specified number of days. Filter by tag, limit, and include notes as needed.

Instructions

List to-dos completed within the last days days (from the Logbook).

Useful for syncing finished tasks back into other systems. days defaults to 30.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Only return to-dos carrying ANY of these tags (comma-separated, case-insensitive). Empty = no tag filter.
`days`	No	Look back this many days.
`limit`	No	Return at most N to-dos (0 = all). Applied AFTER the tag filter.
`include_notes`	No	False drops the `notes` field — notes dominate the payload.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.3.0Aug 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / days / description
```
Added value: +"Look back this many days."
```
removedInput schema / properties / days / title
```
Removed value: -"Days"
```

addedInput schema / properties / include_notes

Added value: +{
+  "default": true,
+  "description": "False drops the `notes` field — notes dominate the payload.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 0,
+  "description": "Return at most N to-dos (0 = all). Applied AFTER the tag filter.",
+  "type": "integer"
+}

addedInput schema / properties / tag

Added value: +{
+  "default": "",
+  "description": "Only return to-dos carrying ANY of these tags (comma-separated,\ncase-insensitive). Empty = no tag filter.",
+  "type": "string"
+}

removedInput schema / title

Removed value: -"get_completedArguments"

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"get_completedOutput"
```
addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

First observedv0.2.1Jul 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden of behavioral disclosure. It is implicitly read-only ('List') and explains the Logbook scope and default lookback window, but it does not describe output ordering, tag filtering caveats, or other behavior beyond the core listing.

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

Conciseness5/5

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

Two short sentences with no filler. The primary purpose is front-loaded, and each sentence serves a distinct role: defining the core list operation and stating its intended usage context.

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 simple read tool with all parameters documented and an output schema present, the description is mostly complete. It could have explicitly differentiated itself from 'list_todos' or 'search_todos', but for the core operation it is adequate.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The only parameter-related mention in the description, the default of `days` to 30, duplicates what is already in the schema and adds no new information.

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?

The description clearly states the action ('List to-dos completed within the last `days` days') and identifies the resource (completed to-dos) and source (Logbook). It does not explicitly mention sibling tools, but the 'completed' filter makes its scope distinguishable from generic list/search siblings.

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?

The sentence 'Useful for syncing finished tasks back into other systems' gives clear usage context for the tool. There is no explicit when-not-to-use guidance or mention of alternatives, which prevents a higher score.

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

Deploy Server