Skip to main content
Glama

cmdb_reconcile

Merge duplicate CIs, retire stale CIs, or remove orphan CIs to clean up CMDB records. Preview changes with dry_run before applying.

Instructions

Act on duplicate, stale, or orphan CIs — merge, retire, or remove (requires CMDB_WRITE_ENABLED). Supports dry_run mode.

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": "<action>",
      "targets": "<targets>"
    },
    "name": "cmdb_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
actionYesReconciliation action to perform
dry_runNoPreview changes without applying (default true)
targetsYesArray of CI sys_ids to act on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. Addedv4.9.0

TDQS

B3/5.0
Behavior1/5

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

The description says the tool will "remove" CIs, but annotations declare destructiveHint=false, which is a direct contradiction for an operation that deletes orphans and retires stale records. The useful additions (the CMDB_WRITE_ENABLED prerequisite and dry_run support) are genuine, but they do not resolve the safety-profile conflict, so the annotation contradiction governs.

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?

One tight sentence plus a short fragment, with the action set front-loaded before the prerequisite and the dry_run note. Nothing is padded, though the second fragment is thin enough that it could have carried more operational detail instead.

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 four-parameter mutation tool with no output schema, the definition omits key operational facts: which record survives a merge, whether retire/remove is reversible, and what happens to references of removed CIs. The prerequisite and dry_run mention partially compensate, but an agent must open the schema and guess at the rest.

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%, with every parameter documented including the dry_run default of true and the async job/poll-with-get_job behavior. The description's only parameter mention, "Supports dry_run mode," adds nothing beyond the schema, so the baseline of 3 is appropriate.

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?

"Act on duplicate, stale, or orphan CIs — merge, retire, or remove" names concrete verbs and the resource, and the framing as the acting/mutating counterpart to the cmdb_find_* family is inferable from the wording. It stops short of explicitly naming which finder feeds which action, so the differentiation is implicit rather than stated.

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 gating condition (CMDB_WRITE_ENABLED) and the dry_run option give real pre-call context, and usage after discovery is implied by the duplicate/stale/orphan targeting. There is no explicit when-to-use versus cmdb_find_duplicates/cmdb_find_stale/cmdb_find_orphans, nor any statement of when not to act.

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

Deploy Server

Other Tools