Skip to main content
Glama

cmdb_find_duplicates

Read-only

Detect duplicate configuration items by scanning a CI class and grouping records that match specified fields. Set the scan limit or run as a background job for larger checks.

Instructions

Find duplicate CIs by matching on specified fields (in-memory grouping)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cmdb_find_duplicates"
  }
}

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.
limitNoMax CIs to scan (default 100)
ci_classNoCI class table (default cmdb_ci)
match_fieldsNoFields to match on for duplicate detection (default: name, serial_number, ip_address)

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.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds 'in-memory grouping', which usefully hints that matching is done client-side over a scanned set rather than by a server-side duplicate index, but it does not explain the consequences (scan cap of 100 CIs by default, potential job switch), and those are only visible in the schema.

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?

A single front-loaded clause with the core action first and the mechanism in a parenthetical — nothing redundant. It is arguably too terse rather than bloated, but no sentence is wasted.

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?

There is no output schema, and the description never says what comes back — duplicate groups keyed by matched fields, a flat CI list, or a count — which matters a lot for a grouping tool. It also omits the scan-limit behavior and background-job semantics that shape how results are interpreted, so the definition is underspecified for a tool with async execution and no declared return shape.

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 all four parameters (async, limit, ci_class, match_fields) are already documented with defaults in the schema. The description's parenthetical 'in-memory grouping' adds a small amount of meaning about how match_fields is applied, but nothing about how field combinations are evaluated or how results are grouped.

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: 'Find duplicate CIs by matching on specified fields', which is concrete enough that an agent can distinguish it from a plain search. It does not, however, differentiate itself from nearby siblings such as cmdb_find_orphans or cmdb_find_stale, so an agent must infer the boundary from names alone.

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?

There is no when-to-use guidance: nothing says when duplicate detection is the right call versus search_cmdb_ci or the other cmdb_find_* variants, and no prerequisites, exclusions, or cost considerations are given. The agent is left to infer usage entirely from the one-line purpose.

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