Skip to main content
Glama

toda_prune

Archives completed TODO items older than a specified number of days by moving them into TODA-archive.md, keeping the active ledger clear.

Instructions

Move done items older than N days into TODA-archive.md

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": "toda_prune"
  }
}

Input Schema

NameRequiredDescriptionDefault
older_than_daysNoDefault 30; counts from the opened date, so 0 archives closed items opened before today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the meaningful non-obvious behavior that items go into TODA-archive.md (implying removal from the active list), but it omits whether the archive file is created if absent, whether the operation is reversible, and whether it prompts for confirmation — significant gaps for a mutating tool.

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?

A single sentence that front-loads the action and the cutoff condition with zero filler. Nothing in it is redundant.

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?

For a one-optional-parameter tool with full schema coverage and no output schema, the description conveys the core effect and destination adequately. The remaining gap is the absence of any note on side effects such as archive-file creation or confirmation behavior.

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?

Schema coverage is 100% and the schema already documents the default of 30 and the 'counts from the opened date' semantics. The description only restates it as 'N days', adding no format or edge-case meaning beyond the parameter definition.

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 names a specific verb (move), a specific resource (done items older than N days), and the destination (TODA-archive.md), making the archival behavior unambiguous. It is distinguishable from the siblings (toda_add, toda_init, toda_list, toda_set) by resource and effect, though it does not explicitly reference any of them.

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?

Usage is implied by 'done items older than N days' — an agent can infer this is the cleanup/archival step to run periodically. There is no explicit guidance on when to prefer this over leaving items in place, no mention of prerequisites, and no note about whether running it repeatedly is safe.

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