ADHD Progress Hub

Overview Schema Source Related Servers Discussions Admin

upsert_thread

Create or update a single finishable work thread to track an independent outcome. Use for new threads or explicit updates; for routine progress checkpoints, prefer upsert_progress to keep notes in sync.

Instructions

Create a new finishable work thread or explicitly update one.

    One thread should represent one independently finishable outcome, not a
    whole project. Pass thread_id when updating a known thread. For routine
    checkpoints on active work, prefer upsert_progress so progress notes and
    PROGRESS.md stay in sync.

Input Schema

TableJSON Schema

Name	Required	Default
`goal`	No
`focus`	No
`energy`	No	unknown
`status`	No	open
`summary`	Yes
`chat_ref`	No
`thread_id`	No
`next_steps`	No
`resume_step`	No
`source_tool`	No
`project_slug`	No
`blocked_reason`	No
`transcript_ref`	No
`workspace_path`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.12.0Sep 14, 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 full burden. It discloses the create-vs-update branching via thread_id and the domain rule that one thread equals one finishable outcome. However, it does not explain update merge/replace semantics, persistence side effects, or any auth/permission requirements.

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 description is concise and front-loaded with the primary create/update purpose. The extra guidance about finishable outcomes and upsert_progress earns its place, though the formatting with indentation is slightly loose.

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

Completeness2/5

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

For a 14-parameter upsert tool with no annotations and no schema descriptions, this description is too thin. It provides good routing and purpose, but an agent cannot confidently populate fields like goal, focus, chat_ref, transcript_ref, or source_tool based on this text. The output schema covers return shape, so that is not a gap, but field-level semantics remain unclear.

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

Parameters2/5

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

The schema has 14 parameters with 0% description coverage, so the description must compensate. The only parameter given real meaning is thread_id ('Pass thread_id when updating a known thread'); the required summary field and most other fields receive no clarification.

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: 'Create a new finishable work thread or explicitly update one.' It clearly distinguishes the tool from siblings like upsert_progress and mark_done by defining a thread as a single finishable outcome.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool versus alternatives: 'For routine checkpoints on active work, prefer upsert_progress.' It also gives a concrete update condition: 'Pass thread_id when updating a known thread.'

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