ADHD Progress Hub

Overview Schema Source Related Servers Discussions Admin

session_digest

Builds a session-start resume digest from stale threads, due reminders, and progress notes. Query and energy level filter relevant work to current capacity, helping agents resume context.

Instructions

Build the session-start resume digest for the current work context.

    Use after resolve_project. It combines relevant stale/open threads, due
    reminders, and the progress wiki snippet; query narrows overlap relevance
    and energy can filter work to the operator's current capacity.

    Includes a `guidance` object (expected versions + last local verification
    status). The Hub cannot inspect the client's checkout — run
    `adhd-hub doctor --project` locally (or call `report_guidance_health`
    after a local check) so this field becomes meaningful.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`energy`	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

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains what the digest combines, how query and energy alter output, that the Hub cannot inspect the client checkout, and that the guidance field depends on a local verification step. It stops short of explicitly stating whether the call has side effects, though the 'build/combine' framing strongly implies a read-only digest.

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?

Front-loaded purpose in the first sentence, followed by composition/behavior and a focused caveat about the guidance object. Each section earns its place, and the organization makes it easy to skim; the doctor instructions add a little length but are functionally relevant.

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

Completeness3/5

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

The output schema exists, so return values need not be restated. The description covers the prerequisite, digest components, parameter effects for two inputs, and the guidance caveat. However, workspace_path is omitted entirely, and with no annotations the side-effect profile is left to inference, leaving a clear but not fatal completeness gap.

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 supply parameter meaning. It does for query ('narrows overlap relevance') and energy ('filter work to the operator's current capacity'), but workspace_path is never mentioned, and there is no explanation of null/default behavior. The two explained parameters add real value, but one of the three inputs is left unexplained.

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?

Opens with a specific verb and resource — 'Build the session-start resume digest for the current work context' — and enumerates the digest's components (stale/open threads, due reminders, progress wiki snippet). This makes it readily distinguishable from sibling tools like list_open_threads, get_overview, or resolve_project without needing to inspect their schemas.

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?

Explicitly states the sequencing prerequisite 'Use after resolve_project' and offers a concrete alternative path for making the guidance field meaningful via local doctor or report_guidance_health. It does not spell out when not to use this tool, but the guidance is clear and actionable.

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