Skip to main content
Glama

implement_review_suggestions

Converts selected code or architecture review findings into actionable tasks or feature work, enabling orchestrators to act on review suggestions by severity and issue choice.

Instructions

Convert review findings into new features that can be worked on. This allows the orchestrator to act on code/architecture review suggestions by creating actionable tasks.

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>"
    },
    "name": "implement_review_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoSelectNoAuto-select all issues at or above minSeverity (default: false)
projectDirYesAbsolute path to the project directory
reviewTypeNoWhich review findings to use (default: both)
minSeverityNoMinimum severity level to include (default: warning)
issueIndicesNoSpecific issue indices to implement (0-based). If not provided, shows available issues.

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?

With no annotations, the description carries the full disclosure burden, yet it never says whether this writes code, mutates a backlog, or is reversible, nor what happens to findings already converted. The name 'implement' suggests code changes while the text says it creates tasks, leaving a real ambiguity about side effects. No mention of permissions, idempotency, or rate/state constraints.

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?

Two short sentences, front-loaded with the core action, with no filler. The second sentence largely restates the first in orchestrator terms rather than adding new information, which keeps it just under maximum.

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 5-parameter mutation-oriented tool with no output schema, the description is minimal: it omits the two-phase behavior encoded in the schema (omitting issueIndices shows available issues rather than implementing anything) and says nothing about what comes back. Annotations are absent, so that missing behavioral layer is not compensated elsewhere.

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 autoSelect, minSeverity, reviewType, issueIndices, and projectDir are already fully documented. The description adds no additional meaning about parameter interaction, such as what happens when issueIndices is omitted. Baseline 3 applies when the schema does the heavy lifting.

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 states a concrete transformation: converting review findings into new, workable features, scoped to code/architecture reviews. It is specific about the resource being consumed (review findings) and produced (actionable tasks/features). It does not name a sibling like get_review_results or add_feature to draw a boundary, so it stops 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 Guidelines2/5

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

It says the tool 'allows the orchestrator to act on ... review suggestions', which hints at a post-review context, but gives no explicit when-to-use rule, no prerequisite (e.g., a completed run_review), and no guidance on when to prefer get_review_results or add_feature instead. The agent must infer the workflow position.

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