Skip to main content
Glama

list_ai_inventory_cis

Read-only

Lists AI and MCP configuration items in the CMDB, including functions, servers, applications, and model deployments; use gaps mode to find CIs without assets or assets without CIs.

Instructions

AI and MCP configuration items in the CMDB: AI functions (cmdb_ci_function_ai), MCP servers (cmdb_ci_function_mcp, with mcp_url), AI applications (cmdb_ci_appl_ai_application) and AI model deployments (cmdb_ci_ai_model_deployment), with owner, life cycle and linked AI Control Tower asset. mode=gaps finds CIs with no asset and AI assets (alm_ai_digital_asset) with no CI. Read-only.

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": "list_ai_inventory_cis"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNolist (default) or gaps (CI without asset, asset without CI)
nameNoName contains
limitNoMax records per class (default 25)
ci_typeNoWhich CI class (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A4.2/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 the 'Read-only' sentence repeats rather than adds. The description does contribute field-level context (owner, life cycle, linked AI Control Tower asset, mcp_url on MCP servers), but says nothing about pagination behavior beyond the limit parameter or result ordering.

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?

Two compact sentences, front-loaded with the resource and then the class enumeration, with no filler phrases. The class-list sentence is dense but every clause carries distinct information about what is returned.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing returns and does so: the CI classes, key fields exposed, and the two gap directions. Combined with annotations covering the safety profile and a fully documented schema, an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by mapping ci_type values to their underlying CMDB tables (e.g., ai_function -> cmdb_ci_function_ai, mcp_server -> cmdb_ci_function_mcp) and by spelling out the gaps mode semantics. It still leaves name matching and limit truncation behavior to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verb+resource: lists AI/MCP configuration items in the CMDB, and enumerates the four concrete CI classes (cmdb_ci_function_ai, cmdb_ci_function_mcp, cmdb_ci_appl_ai_application, cmdb_ci_ai_model_deployment) plus the asset gap mode. An agent knows exactly what population this returns without opening a schema.

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?

Clearly explains the two modes: default listing versus mode=gaps for CIs without an asset and AI assets without a CI, which is actionable when-to-use guidance. It does not name an alternative tool or state exclusions, so it falls short of a 5.

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