Skip to main content
Glama

toda_list

List deferred issues from the markdown ledger, filtering by open, sleeping, or closed status, ref, or keyword, with optional archive scanning.

Instructions

List deferred items (default: open + sleeping)

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoSubstring match within the ref: segment only
statusNoDefaults to ["o","s"]
keywordNoSubstring match on the whole line (case-insensitive)
include_archiveNoAlso scan TODA-archive.md

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only restates the default status filter. It does not state that the operation is read-only, whether results are ordered or limited, what fields each item returns, or whether archived items are excluded by default.

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?

A single front-loaded line with zero filler, and the default behavior is surfaced first. It is efficient but borders on under-specification given the absence of other behavioral context.

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 simple four-optional-parameter listing tool with full schema coverage and no annotations, the definition is minimally adequate. It stops short of describing result shape or archive-scanning behavior, and no output schema exists to compensate.

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 description coverage is 100%, so all four parameters (ref, status, keyword, include_archive) are already documented with types and matching semantics. The description adds only the default status set, which the schema also declares, so it does not exceed the baseline.

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?

States a specific verb (List) and resource (deferred items), which distinguishes it from the mutation-oriented siblings toda_add, toda_prune, and toda_set. However, 'deferred items' is domain jargon that leaves the underlying data model somewhat opaque without prior knowledge of the system.

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

Usage Guidelines2/5

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

The only usage signal is the parenthetical default status filter (open + sleeping). There is no guidance on when to use this versus the sibling tools, no mention of what include_archive enables in practice, and no exclusions or prerequisites.

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