Keelen

Get Project Digest

project_digest

Read a compact progress digest for one project (delivery, activity, holds, next decision).

    Returns the closed MCP projection: delivery counts and the five newest
    delivered items, a recent loop-activity count, current holds, the single
    highest-priority open decision, and `more_decisions`. Two steering fields
    are ALWAYS present: `next_action` is `"call_tool"` with
    `next_tool="list_escalations"` when a decision exists, otherwise
    `"none"` with `next_tool: null`. `since` is an optional ISO-8601
    timestamp with a timezone; it defaults to 24 hours ago and is clamped to
    the last seven days. This tool is **off by default and not generally
    available**: it is registered only when the server was started with
    `KEELEN_PROGRESS_DIGEST_ENABLED` enabled, and a live disable refuses
    calls until restart. Tenant-scoped: a project outside the caller's
    workspace 404s.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	No
`project_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A3.8/5.0

Behavior2/5

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

The description is unusually rich about behavior beyond the annotations: feature-flag registration, live-disable refusal, tenant scoping with 404, and the mandatory steering fields. However, it opens with 'Read' while the annotations declare readOnlyHint=false and idempotentHint=false, which is an inconsistency between stated and structured behavior.

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-loads the one-line purpose, then return shape, then availability constraints. It is longer than average but each sentence adds operational information; the steering-field sentence is dense but justified by non-obvious semantics.

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?

Although an output schema exists, the description still supplies the semantics an agent needs (next_action/next_tool contract, more_decisions, clamping window) plus the gating and scoping preconditions. Nothing needed to invoke it correctly is missing.

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 description coverage is 0%, so the description must carry the load, and it does for `since`: optional ISO-8601 timestamp with timezone, defaults to 24 hours ago, clamped to the last seven days. `project_id` is only indirectly covered via the tenant-scoping sentence, leaving one parameter thin.

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?

States a specific verb and resource ('Read a compact progress digest for one project') and enumerates the exact contents (delivery counts, five newest delivered items, activity count, holds, top open decision, more_decisions). An agent can distinguish this from the sibling project_status without opening either schema.

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

Usage Guidelines3/5

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

It gives strong availability gating (off by default, registered only with KEELEN_PROGRESS_DIGEST_ENABLED, live disable refuses calls, tenant-scoped 404) but never says when to prefer this over project_status or list_escalations. The when-to-use is implied by the return contents rather than stated against alternatives.

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

All Keelen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.