Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

tasks-completed-this-week

Retrieve all tasks completed in the past 7 days to prepare weekly standup updates and review recent progress.

Instructions

Return all tasks completed in the last 7 days. Useful for weekly standups.

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": "tasks-completed-this-week"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden of behavioral disclosure. "Return" implies a read, but the description never states whether "last 7 days" is keyed on completion timestamp or due date, what timezone applies, whether results are ordered, or whether output is capped — all material for a time-windowed query.

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?

Two short sentences with the scope front-loaded and the use case trailing as supporting context. No filler, no restatement of the tool name, nothing that could be cut without losing information.

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?

For a zero-parameter, no-output-schema read tool this covers the essentials: what is returned and the time window. It is still incomplete on the definition of "completed" and on result ordering or size, which an agent would need to answer a follow-up question accurately.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; the time window is fixed rather than parameterized, which the description correctly conveys.

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?

"Return all tasks completed in the last 7 days" states a specific verb (return), a specific resource (tasks), and a scope constraint (completed within 7 days), which separates it from list-tasks and search-tasks by behavior. It stops short of naming those siblings explicitly, so an agent must infer the distinction from the scope wording alone.

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?

"Useful for weekly standups" supplies a concrete usage context, which is more than nothing. However, it gives no when-not guidance and never points to an alternative such as list-tasks or search-tasks for broader or historical queries, leaving routing to inference.

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