Skip to main content
Glama

cmdb_find_stale

Read-only

Finds operational configuration items not updated within a specified day threshold, helping you identify stale CIs for review or cleanup.

Instructions

Find CIs not updated within a given number of days that are still operational

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

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 stale CIs to return (default 50)
ci_classNoCI class table (default cmdb_ci)
days_thresholdNoNumber of days since last update to consider stale (default 90)

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

A3.5/5.0
Behavior3/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 one genuine behavioral detail, that results are restricted to CIs 'still operational', but never defines what operational means (status filter? install status?) or how that interacts with the ci_class parameter. No guidance on result volume beyond the schema's own limit description.

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 compact sentence with the verb front-loaded and no filler. It is well sized for the tool's simplicity, though the trailing qualifier 'still operational' is left dangling without explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, zero-required, read-only query tool with a fully documented schema and no output schema, the description covers the essential purpose and the temporal criterion. The one material gap is the undefined 'operational' filter, which is the tool's distinguishing behavioral trait and could surprise an agent expecting all stale CIs.

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%, including defaults for limit (50), ci_class (cmdb_ci), days_threshold (90), and async behavior with get_job polling. The description only restates the days_threshold concept ('within a given number of days') and adds nothing about ci_class or the async path, so the baseline 3 applies.

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 plus resource plus scope: 'Find CIs not updated within a given number of days that are still operational.' An agent immediately knows this retrieves stale configuration items. It does not, however, differentiate itself from sibling searchers like cmdb_find_orphans or search_cmdb_ci, so the boundary between them must be inferred.

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?

Usage is implied by the phrase 'not updated within a given number of days' combined with 'still operational', which tells the agent this is a staleness audit rather than a general search. There is no explicit when-to-use, when-not-to-use, or named alternative among the cmdb_find_* family.

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