Skip to main content
Glama

toda_add

Append a deferred issue to TODA.md—auto-creating the file—and record why it is postponed plus the trigger for revisiting it.

Instructions

Append a deferred item to TODA.md (auto-creates the file)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "what": "<what>",
      "why_deferred": "<why_deferred>",
      "revive_when": "<revive_when>"
    },
    "name": "toda_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoSpace-separated refs: commit shas, gh:#123, tag names
whatYesOne-line description of the issue
whereNoLocation token like src/x.ts:42 (default -)
statusNoDefaults to o (open)
revive_whenYesTrigger condition to revisit
why_deferredYesWhy it is not being fixed now

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden of disclosing behavior. It does disclose one meaningful behavioral trait, that the file is auto-created if it is missing, and 'append' implies that existing entries are preserved. It does not say what is returned, whether duplicate entries are detected, where TODA.md is written with respect to the working directory, or whether the write can fail because of permissions.

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 whole definition is one compact sentence with the action and the file named up front, followed by the auto-creation caveat in parentheses. There is no filler, and the most important fact is presented first.

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 6-parameter mutation tool with no annotations and no output schema, one sentence is thin. The schema covers all parameters well, but the description says nothing about the return value or the outcome of the call, or about how duplicates and concurrency are handled. It is adequate but leaves real gaps for an agent calling a write tool.

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%, and every parameter including the enum values o/s/x and the default for 'where' is documented inline. The description adds no additional semantics about the parameters beyond that, so the baseline of 3 is appropriate when the schema already carries the full explanation.

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 gives a specific verb and resource: 'Append a deferred item to TODA.md', and adds an important scope detail, that the file is auto-created. That is a clear purpose. It does not, however, explicitly say how it differs from a sibling such as toda_set, which is likely a replace or update operation, so an agent must infer the append-versus-set distinction.

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?

There is no explicit statement of when to use this tool versus toda_set or toda_list, and no statement of when not to use it. Usage is only implied by the word 'deferred' and by the required 'why_deferred' and 'revive_when' parameters, which signal that this is for logging issues that are intentionally postponed. A short line about when to choose toda_add over toda_set would raise the score.

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