Skip to main content
Glama

Complete Action Item Tool

retro.actions.complete
Idempotent

Marks an action item as completed. Requires mcp:write scope.

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": {
      "action_item_id": "<action_item_id>"
    },
    "name": "retro.actions.complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_item_idYesThe ID of the action item to mark as completed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so retry safety and non-destructiveness are covered. The description adds meaningful context beyond that by disclosing the required mcp:write scope. It does not explain what happens to the action item beyond status change, but the annotation bar is already partly met.

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?

Two short sentences with zero waste. The primary action is front-loaded, followed immediately by the operational prerequisite.

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

Completeness4/5

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

For a single-parameter mutation tool with annotations covering idempotency and non-destructiveness, the definition is nearly complete. It includes the auth requirement and clear action. Minor omission: it does not state what happens if the item is already completed, though idempotentHint implies a safe no-op.

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 coverage is 100% and there is a single parameter fully documented in the schema. The description adds no parameter-specific detail, so the baseline of 3 is appropriate 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 specific verb and resource: 'Marks an action item as completed.' This is unambiguous about what the tool does. However, it does not differentiate from the sibling retro.actions.update, which likely could also change status, so an agent still has to infer which to use.

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 'Requires mcp:write scope' note gives a useful prerequisite, but there is no explicit guidance on when to use this versus retro.actions.update or retro.actions.list. Usage is implied by the verb 'completed' but not contrasted with alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources