Skip to main content
Glama

cmdb_find_orphans

Read-only

Find configuration items with no relationships in cmdb_rel_ci to identify orphaned CIs for cleanup. Optionally set a result limit and CI class.

Instructions

Find CIs with no relationships in cmdb_rel_ci

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_orphans"
  }
}

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 orphan CIs to return (default 50)
ci_classNoCI class table (default cmdb_ci)

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing beyond that: no statement on scan cost, whether relationships in other tables are considered, what an empty result means, or ordering/pagination behavior for the returned orphans. For a potentially expensive cross-table scan, that is a meaningful gap.

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 sentence with zero filler; the core condition is stated immediately. It is arguably too terse for the tool's complexity, but no sentence is wasted.

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?

The tool is a low-parameter read query with a fully described schema and no output schema, so the burden is modest. Still, the description says nothing about what a returned orphan record contains or how the 'no relationships' condition is evaluated across the relationship table, leaving key context to inference.

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 async, limit, and ci_class are already documented in the schema, including defaults and polling semantics. The description contributes no additional meaning about how limit interacts with large result sets or when to override ci_class.

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 ('Find') plus a precise resource and condition ('CIs with no relationships in cmdb_rel_ci'). An agent can immediately distinguish it from siblings like cmdb_find_duplicates or cmdb_find_stale, though the description never explicitly contrasts itself with them.

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, no prerequisites, and no mention of alternative tools. The agent must infer from the name alone whether this is the right query for a given cleanup or hygiene task.

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