Skip to main content
Glama

mark_complete

Marks a feature as completed or failed after verifying worker output or tests, with automatic retries for failed features by default.

Instructions

Mark a feature as completed or failed. Call this after verifying the worker's output or running tests. When marking as failed, auto-retry is enabled by default (up to maxRetries attempts).

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>",
      "success": "<success>"
    },
    "name": "mark_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional notes about the completion or failure
successYesWhether the feature was completed successfully
featureIdYesID of the feature to mark
maxRetriesNoMaximum retry attempts for failed features (default: 3). Set to 0 to disable auto-retry.
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose a non-obvious side effect: marking a feature failed enables auto-retry by default up to maxRetries attempts. It leaves some behavior unexplained, such as whether the call is idempotent, what state transitions occur, or whether a retry is dispatched immediately, so it is strong but not exhaustive.

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?

Three short sentences ordered purpose, then timing, then behavioral caveat. Nothing redundant, and the most decision-relevant facts come 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 five-parameter mutation with no annotations and no output schema, the description is adequate but thin: it never says what the call returns or what the caller should do next after the feature is marked failed and a retry is queued. An agent can invoke it correctly from the schema plus this text, but cannot predict the resulting side effects fully.

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 every parameter is already documented, which sets the baseline at 3. The description reinforces maxRetries semantics by tying it to the failure path, but adds no format or constraint detail beyond the schema.

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: 'Mark a feature as completed or failed', naming the two terminal states the operation sets. It is clearly distinct from siblings like add_feature or enqueue_feature, though it never explicitly names a contrasting sibling, which keeps it short of a 5.

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

Usage Guidelines4/5

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

It states a concrete trigger condition: call after verifying the worker's output or running tests. That is real when-to-use guidance. It stops short of a 5 because it offers no when-not guidance or named alternative for cases such as marking a feature complete before verification.

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