Skip to main content
Glama

update_adr_status

Change the lifecycle status of an Architecture Decision Record (ADR) from Proposed to Accepted, Deprecated, or Superseded to track decision evolution.

Instructions

Update the status of an ADR: Proposed → Accepted → Deprecated → Superseded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adr_idYesADR ID to update
statusYesNew status
superseded_byNoID of the replacing ADR (required when status is Superseded)

Implementation Reference

  • The 'update_adr_status' tool registration and handler implementation in the MCP server.
    server.registerTool('update_adr_status', {
      description: 'Update the status of an ADR: Proposed → Accepted → Deprecated → Superseded',
      inputSchema: {
        adr_id:        z.number().describe('ADR ID to update'),
        status:        z.enum(['Proposed', 'Accepted', 'Deprecated', 'Superseded']).describe('New status'),
        superseded_by: z.number().optional().describe('ID of the replacing ADR (required when status is Superseded)'),
      },
    }, async ({ adr_id, status, superseded_by }) => {
      const adr = getADR(adr_id);
      if (!adr) throw new Error(`ADR ${adr_id} not found`);
      if (status === 'Superseded' && !superseded_by) {
        throw new Error('superseded_by is required when setting status to Superseded');
      }
    
      updateADRStatus(adr_id, status, superseded_by ?? null);
    
      const updated = { ...adr, status, superseded_by: superseded_by ?? null };
      exportADRFile(adr_id, updated, adr.session_id);
    
      const note = superseded_by ? ` (superseded by ADR-${superseded_by})` : '';
      return { content: [{ type: 'text', text: `ADR-${adr_id} updated to "${status}"${note}` }] };
    });
  • db.js:72-75 (helper)
    The database helper function 'updateADRStatus' that performs the SQL update.
    export function updateADRStatus(id, status, superseded_by = null) {
      db.prepare('UPDATE adrs SET status = ?, superseded_by = ? WHERE id = ?')
        .run(status, superseded_by, id);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a mutation operation ('Update') but doesn't state permission requirements, whether changes are reversible, or what happens on success/failure. The status transition list is helpful but doesn't cover behavioral traits like validation rules or side effects (e.g., notifications).

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?

The description is a single, efficient sentence that front-loads the core action ('Update the status of an ADR') followed by specific status values. There's zero wasted text, and every word contributes directly to understanding the tool's purpose.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address what the tool returns, error conditions, or important behavioral aspects like whether 'superseded_by' is validated. The status transition list is useful but insufficient for safe invocation without additional 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 schema already documents all three parameters thoroughly. The description adds no parameter-specific information beyond implying status transitions, which the schema's enum already covers. This meets the baseline for high schema coverage but doesn't provide additional semantic context.

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 verb ('Update') and resource ('status of an ADR') with specific status transitions listed. It distinguishes this tool from siblings like 'check_stale_adrs', 'generate_adr', or 'link_adrs' by focusing on status updates rather than creation, review, or linking. However, it doesn't explicitly mention what ADR stands for (Architectural Decision Record), which could help further differentiate it.

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?

The description provides no guidance on when to use this tool versus alternatives like 'review_adr' or 'link_adrs'. It lists status transitions but doesn't specify prerequisites (e.g., needing review before acceptance) or exclusions (e.g., not for initial creation). This leaves the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wooxogh/adr-mcp-setup'

If you have feedback or need assistance with the MCP directory API, please join our Discord server