Skip to main content
Glama

consolidate_apply

Destructive

Luxury only (payments currently off): apply one approved dry-run diff in your suite with a 30-day snapshot and reload manifest. Requires session, dry_run_id and approve=true.

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": {
      "session": "<session>",
      "dry_run_id": "<dry_run_id>",
      "approve": "<approve>"
    },
    "name": "consolidate_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
approveYes
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
dry_run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds value beyond that by disclosing a 30-day snapshot and reload manifest, giving the agent a concrete recovery path (restore) and the approval gate required before a destructive apply. It still does not say what happens on partial failure or whether the diff can be re-applied, but the added context is meaningful.

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 sentences, action and gating requirements up front, side effects second. The unexplained 'Luxury only (payments currently off)' parenthetical is the one piece that does not clearly earn its place, but overall it is tight for a destructive multi-effect operation.

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 destructive, non-idempotent mutation with no output schema, the description does well to name the snapshot and reload manifest. It remains silent on error/rollback behavior, whether the operation is scoped to the calling session's suite, and what the caller gets back after apply, leaving gaps an agent would want before invoking.

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?

With only 33% schema coverage, the description must compensate, and it does explain that a dry-run diff must be 'approved' (linking dry_run_id to a prior dry run) and that approve must be true. However, it merely restates that session and dry_run_id are required without adding format, origin, or lifecycle meaning, leaving the dry_run_id semantics under-specified.

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?

States a specific verb and object: 'apply one approved dry-run diff in your suite', plus the side effects (30-day snapshot, reload manifest). An agent can distinguish it from preview_consolidation or consolidate because it says 'apply', though the leading 'Luxury only (payments currently off)' clause is unexplained and adds noise before the actual purpose.

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?

'Apply one approved dry-run diff' implies a prior dry run must exist and be approved, which weakly routes agents to preview_consolidation/consolidate, and the 'Luxury only (payments currently off)' preamble signals availability gating. But no sibling is named and there are no explicit when/when-not conditions, so the agent must infer the workflow.

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