Skip to main content
Glama

cmdb_impact_analysis

Read-only

Analyze a configuration item's CMDB relationships to show which CIs are affected by its change or outage and which dependencies it relies on.

Instructions

Analyze the impact of a Configuration Item change or outage: what depends on it (affected if it fails) and what it depends on

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": {
      "ci_sys_id": "<ci_sys_id>"
    },
    "name": "cmdb_impact_analysis"
  }
}

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.
depthNoRelationship depth to traverse (default: 2)
ci_sys_idYesCI sys_id to analyze
directionNoimpacted = CIs that depend on this one, dependencies = CIs it depends on, both (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
      +}
    • addedInput schema / properties / direction
      Added value: +{
      +  "description": "impacted = CIs that depend on this one, dependencies = CIs it depends on, both (default)",
      +  "enum": [
      +    "both",
      +    "impacted",
      +    "dependencies"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.0.2

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds nothing behavioral beyond that. It does not mention that deep traversals can be slow or spill into a background job, nor does it describe the shape of the analysis result — an agent must discover the async fallback only from 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 sentence with the verb and scope front-loaded and no filler. It is dense but readable; the colon-plus-parenthetical construction packs both directions efficiently.

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 read-only traversal tool with rich schema coverage this is adequate, but with no output schema the description never indicates what comes back (CI lists, paths, direction of each edge) or how results scale with depth. An agent knows what the tool asks for but not what it receives.

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 baseline is 3. The description's gloss on impacted vs dependencies largely restates what the direction enum already documents, and it adds nothing about depth or async semantics.

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+resource ('Analyze the impact of a Configuration Item change or outage') and defines both traversal directions ('what depends on it' vs 'what it depends on'). It is clearly distinguishable from sibling finders like cmdb_find_orphans or cmdb_services_for_ci, though it never names an alternative explicitly.

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?

The framing 'change or outage' gives a clear trigger context for when this tool applies, and the parenthetical clarifies what an agent should expect. There is no when-not guidance and no named alternative for adjacent questions such as which services use a CI.

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