Skip to main content
Glama

generate_standup_report

Generate a standup report from logged tasks, grouping by tag and adding an optional weekly rollup for done, in progress, and blocked items.

Instructions

Generate a clean, bulleted standup message from yesterday and today.

Automatically groups items by tag/project if any logged tasks have one.
Set include_weekly=True to append a rollup covering the last `range_days`
days (default 7). The rollup follows the standard three-question standup
format — Done / In Progress / Blocked — for that whole period, not just
completed items, so it works for a weekly retro, a 1:1, or any custom
stretch of time by adjusting range_days.

Uses standard Markdown (**bold**, _italic_, - bullets) so it renders
cleanly in Claude's chat UI. If pasting into Slack, swap ** for single
* around headers (Slack uses single asterisks for bold).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
range_daysNo
include_weeklyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses automatic grouping by tag/project, the rollup's three-question format over the full period rather than only completed items, and Markdown/Slack formatting behavior. It does not explicitly confirm the tool is read-only or state an empty-data edge case, but these are minor for a report generator.

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 front-loaded with the core purpose and each paragraph adds distinct value. It is slightly longer than strictly necessary, with the Slack formatting note being peripheral to invoking the tool, but it remains well-structured and free of redundancy.

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?

For a two-parameter, zero-annotation tool with an output schema, the description covers invocation semantics, parameter effects, output formatting, and common use cases. Nothing essential for calling it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully explains both parameters: include_weekly=True appends the rollup, and range_days controls the lookback period with a default of 7. This adds real meaning beyond the raw schema names and types.

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 exactly what it does: 'Generate a clean, bulleted standup message from yesterday and today.' The verb+resource is specific and clearly distinct from the task-logging, status-updating, and checklist sibling tools, so an agent can select it without opening 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?

Provides clear usage context: the default yesterday/today behavior, the optional weekly rollup, and explicit use cases (weekly retro, 1:1, custom stretch via range_days). It does not list exclusions or name alternatives, but the sibling tools are functionally distinct enough that the intended scope is clear.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rominap22/standup-journal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server