feature-tracker-mcp

feature_update

Update a tracked feature item's status, title, body, or priority, with each change recorded in append-only history and stamped against the current git commit.

Instructions

Change a tracked item: status, title, body or priority. Every change is recorded in the append-only history, stamped with the git commit it was made against.

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": {
      "id": "<id>"
    },
    "name": "feature_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	e.g. DIP-17
`cwd`	No	Directory identifying the project and the tree. Defaults to this session's working directory, which in a git worktree is that worktree.
`body`	No
`note`	No	Why it changed.
`actor`	No
`title`	No
`status`	No
`priority`	No
`acceptance`	No	What done looks like, concretely enough to test.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries full weight. It explicitly discloses a meaningful behavioral trait: every change is appended to an append-only history stamped with the git commit it was made against. This gives the agent valuable expectations about auditability and mutability beyond the bare 'change' verb, though it does not cover permissions or reversibility.

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 with no filler. The core action and scope are front-loaded, and the audit-history behavior is appended concisely. Every sentence contributes useful information.

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

Completeness2/5

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

For a 9-parameter mutation tool with no annotations and no output schema, the description is too terse. It does not explain partial-update semantics, the intended use of actor/acceptance/note, or what the caller should expect back after invoking the tool. The schema helps, but the combination of high parameter count and lack of output schema leaves significant ambiguity.

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 44%, so the description needs to compensate for the undocumented parameters. It does add value by naming title, body, and priority as changeable fields, which the schema leaves somewhat opaque. However, it does not clarify the purpose of actor, acceptance, note, or how omitted fields behave during a partial update.

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 uses a specific verb and resource: 'Change a tracked item' and enumerates the mutable fields: status, title, body, or priority. This clearly distinguishes the tool from siblings such as feature_propose, feature_list, and feature_history, which are about creating, listing, or inspecting items rather than modifying 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?

The phrase 'tracked item' implies this is for modifying an existing item rather than proposing or listing one, but no explicit when-to-use, when-not-to-use, or alternative tool is named. It does not mention, for example, that feature_propose is the right choice for new items or feature_reassign for reassignment.

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

Deploy Server