ADHD Progress Hub

Overview Schema Source Related Servers Discussions Admin

session_digest

Build a work-resume digest from open threads, due reminders, and progress notes, optionally filtered by query and current energy level.

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.

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

A3.7/5.0

Behavior3/5

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

No annotations are present, so the description is the only behavioral source; it does disclose that the tool combines multiple sources and that query/energy filter the result. However, it does not explicitly state whether the digest is read-only, whether invoking it mutates or stores anything, or what permissions are needed, leaving side-effect behavior under-specified.

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?

Three concise sentences: purpose first, usage cue second, then input-specific behavior. No filler or redundant restatement.

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 description covers purpose, one usage precondition, and two of three optional parameters, and an output schema exists to cover return shape. The missing workspace_path semantics and silent assumptions about side effects make it slightly incomplete for a tool with no annotations.

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?

With 0% schema description coverage, the description is the main semantic source for parameters. It explains query (narrows overlap relevance) and energy (filters to operator capacity), but workspace_path is never described, so a significant parameter is left unexplained.

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 identifies a specific deliverable ('session-start resume digest') and enumerates its composition (stale/open threads, due reminders, progress wiki snippet). It is clear about scope but does not explicitly contrast it with sibling tools like get_overview or list_open_threads, so sibling differentiation is weaker.

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?

Gives an explicit sequence cue, 'Use after resolve_project', which tells the agent when to call it. It also explains how query and energy modify the digest. It does not name exclusions or alternatives beyond the predecessor.

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