Skip to main content
Glama
Sign In
speckitmcp

speckitmcp

by jthom233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

speckit_implement

Track feature implementation progress. Read current tasks and related docs, complete tasks with optional checklist gate, and append implementation notes.

Instructions

Track implementation progress for a feature. Read current tasks and related docs, mark tasks complete (with optional checklist gate), or add implementation notes.

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": {
      "feature_name": "<feature_name>"
    },
    "name": "speckit_implement"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoBypass the checklist gate when completing a task (default false).
notesNoImplementation notes to append.
actionNoAction to perform.read
task_idNoTask ID to mark as complete (e.g., T001).
feature_nameYesName of the feature being implemented.
project_pathNoPath to the spec-kit project root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions an 'optional checklist gate' and that tasks can be marked complete, but does not explain what this gate does, whether it modifies files, or the effects of the 'update_status' action. For a tool capable of mutation, this is a significant gap.

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?

The description is composed of two concise sentences, with the main purpose front-loaded. It avoids unnecessary detail, though 'related docs' is vague, and the omission of update_status makes it slightly incomplete. Overall it is efficient and to the point.

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 multi-action tool with six parameters and no output schema, the description covers most actions but misses the update_status action in the enum. It also lacks details on return values, side effects, and the 'checklist gate' mechanics. The schema fills some gaps, but the description does not fully carry the tool's usage context.

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 the baseline is 3. The description adds no meaningful detail beyond the schema – it references 'optional checklist gate' which is already described in the force parameter. It does not explain the relationship between task_id and feature_name beyond what the schema already states.

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 clearly states the tool's purpose: 'Track implementation progress for a feature' and enumerates primary actions (read, mark tasks complete, add notes). However, it does not explicitly differentiate from sibling tools like speckit_tasks or speckit_status, and it omits the 'update_status' action from the enum, which slightly reduces clarity.

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 through the action list: use this tool when you need to read tasks, complete them, or add notes for a feature. No explicit when-to-use vs alternatives is given, nor are any exclusions mentioned. The description does not reference sibling tools such as speckit_checklist or speckit_tasks, providing only implied context.

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