Skip to main content
Glama
Sign In
mcp-task-tools

mcp-task-tools

by rog0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

standup_generator

Generate daily standup updates by summarizing recently completed tasks, current progress, and blockers from your task list.

Instructions

Generate a daily standup update from the current task list. Shows yesterday (recently completed), today (in progress), and blockers. Uses data from todo_manager.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "standup_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookback_hoursNoHours to look back for completed tasks (default: 24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool generates a standup update from the task list, implying a read operation, but does not explicitly disclose side effects, authentication needs, or limitations. The behavior is implied but not fully detailed.

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?

The description is two sentences, front-loaded with the primary function, and contains no redundant information. Every word serves a purpose.

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

Completeness4/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description adequately explains what the tool does and the structure of its output. It misses details like behavior when no tasks exist, but is largely complete for its complexity.

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?

The parameter 'lookback_hours' is fully described in the schema (100% coverage), so the description does not add new meaning. Baseline is 3 per rubric.

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 clearly states it generates a daily standup update from the current task list, specifying the three sections (yesterday, today, blockers) and the data source (todomanager). This is specific and distinguishes it from sibling tools like priority_sorter and burndown_calculator.

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?

The description implies it's for generating standups, but does not explicitly compare to siblings or provide exclusions. However, the context is clear that it's used for daily progress reporting, and no misleading guidance is given.

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

Deploy Server

Other Tools