apex-memory

set_decision_status

Move a decision record through its lifecycle by rewriting its Status line—proposed to accepted, rejected, superseded, or void—with owner-only updates and required reason or superseding ID.

Instructions

Move a decision record through its life cycle by rewriting its one Status line: proposed -> accepted, rejected or superseded; accepted -> superseded (superseded_by must be an accepted decision) or void (an acceptance made in error; needs reason, which is added to the record as a Void reason line). Owner only.

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": {
      "domain": "<domain>",
      "id": "<id>",
      "status": "<status>"
    },
    "name": "set_decision_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`domain`	Yes
`reason`	No
`status`	Yes
`task_id`	No
`superseded_by`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and explains that the tool mutates the status line, requires ownership, enforces transition rules, and adds a Void reason line when voiding. It does not describe return behavior, error handling, or idempotency.

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 compact and front-loads the core purpose before enumerating the state machine. The dense single-sentence structure with arrows and semicolons is efficient but requires some parsing effort.

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 state-machine mutation with no annotations, no output schema, and 0% schema description coverage, it covers the main transitions and prerequisites. It still omits the meanings of domain/id/task_id and does not explain response or error behavior, leaving meaningful gaps.

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 0%, and the description adds meaning for status transitions, conditional use of superseded_by, and reason for void. However, it leaves domain, id, and task_id unexplained, so several parameters remain undocumented.

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 uses a specific verb, 'Move,' and names the resource, 'decision record,' and clarifies that it rewrites the Status line. It clearly distinguishes the operation as a decision-status state transition, though it does not explicitly name sibling alternatives such as status_item.

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 the allowed lifecycle transitions and important prerequisites: owner-only access, superseded_by must reference an accepted decision, and void requires a reason. It does not explicitly compare this tool against sibling tools or describe when not to use it.

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

Deploy Server