Two behaviours work but aren't surfaced in the tool schemas, so LLM clients won't use them:
-
Natural-language when. Verified: add_todo with when: "next tuesday" produced the correct start_date. The url_scheme.py docstrings mention natural language ("in 3 days", "next tuesday"), but the MCP tool parameter descriptions list only the keywords, YYYY-MM-DD, and YYYY-MM-DD@HH:MM. Clients steered by the schema re-derive dates instead of passing phrases through.
-
reminder_time response field. Todos scheduled with YYYY-MM-DD@HH:MM come back from reads with reminder_time: "HH:MM" (start_date carries the date). Not mentioned in the README or tool docs.
Suggest one line each in the when parameter descriptions and the README parameters section. Can fold into the troubleshooting docs PR if preferred.
Env: things-mcp v0.8.1, macOS, Things 3.
Two behaviours work but aren't surfaced in the tool schemas, so LLM clients won't use them:
Natural-language
when. Verified:add_todowithwhen: "next tuesday"produced the correctstart_date. The url_scheme.py docstrings mention natural language ("in 3 days", "next tuesday"), but the MCP tool parameter descriptions list only the keywords,YYYY-MM-DD, andYYYY-MM-DD@HH:MM. Clients steered by the schema re-derive dates instead of passing phrases through.reminder_timeresponse field. Todos scheduled withYYYY-MM-DD@HH:MMcome back from reads withreminder_time: "HH:MM"(start_datecarries the date). Not mentioned in the README or tool docs.Suggest one line each in the
whenparameter descriptions and the README parameters section. Can fold into the troubleshooting docs PR if preferred.Env: things-mcp v0.8.1, macOS, Things 3.