amazing-marvin-complete-mcp

get_done_items

Read-only

Retrieve tasks completed on a given date, including those scheduled earlier but finished that day. Fetches recent days to catch all completions, caches results, and flags incomplete coverage.

Instructions

Tasks completed on a given date (doneAt within that day, configured timezone) — regardless of priority and deadline. Built on the UNDOCUMENTED endpoint GET /doneItems?date= (missing from the OpenAPI spec and the wiki; live-tested 2026-08-30, may disappear): it filters on the task's day, not on doneAt. A past day is kept on completion both in the app and via the API (the app sets day = today only on unscheduled and future-dated tasks) — hence the date plus lookback_days earlier are fetched and everything is filtered on doneAt. The response always states its coverage: covers_from (= date − lookback) and days_fetched. On a 429/error the fetch stops: incomplete=true, days_missing lists the days not fetched and warning explains; the date's own completions are always included because it is fetched first. Complete results are cached for 30 minutes (cached=true) — repeated calls then cost no API calls; mark_done inserts its task into the cache, delete_task and unmark_done remove theirs. Completions or deletions made in the app show up only once the cache expires. Not covered: a task with a FUTURE day completed via the API (it sits under its day). Tasks only — completed projects are not listed. Items without doneAt (older data) are excluded and counted in skipped_without_done_at. Sorted by doneAt. Cost: one read call per day (~3.1 s each in the queue).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date YYYY-MM-DD on which tasks were completed (configured timezone); omit for today
`lookback_days`	No	Days before the date for which /doneItems is also fetched, to catch tasks scheduled earlier but completed on the date. Each day = one read call (~3.1 s in the queue). Default 7

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.0Aug 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With only readOnlyHint and openWorldHint in annotations, the description goes far beyond by disclosing the undocumented endpoint, filtering on day vs doneAt, future-day caveats, 429/error handling, cache invalidation, excluded items, sorting, and API cost. This is exceptionally transparent behavior documentation.

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?

The purpose is front-loaded and every sentence carries non-obvious information, but the text is dense and somewhat run-on. Given the undocumented endpoint and multiple edge cases, the length is justified, though it could be tightened.

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?

With an output schema present and annotations covering the safe-read nature, the description fully covers selection and invocation: parameters, edge cases, failure behavior, cache semantics, exclusions, and cost. Nothing critical is missing for correct use.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by explaining timezone behavior, that omitting date defaults to today, how lookback_days catches earlier-scheduled tasks, and the per-day cost of each lookback day. This goes beyond the schema descriptions.

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?

The description opens with a specific verb and resource: "Tasks completed on a given date (doneAt within that day, configured timezone)", clearly distinguishing it from sibling tools like get_today_items and get_due_items. It also clarifies scope with exclusions like "regardless of priority and deadline" and "Tasks only — completed projects are not listed."

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 description gives clear context for when to use the tool: to retrieve tasks completed on a specific date, with lookback behavior and exclusions. It does not explicitly name alternative tools or state when not to use it, but the scope is precise enough for an agent to select it correctly.

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