Skip to main content
Glama

import_cmdb_data

Import CI records into a CMDB table via import set. Use this to load configuration item data from arrays of records, with optional async job handling for long runs.

Instructions

Import CI data into CMDB via import set. [Write]

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": {
      "table": "<table>",
      "data": "<data>"
    },
    "name": "import_cmdb_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesArray of records to import
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.
tableYesTarget CMDB table (e.g. cmdb_ci_server)

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. First observedv1.0.2

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare write, non-idempotent, non-destructive, and open-world behavior, so the '**[Write]**' tag adds nothing. The description omits what happens on partial failure, whether existing CIs are updated or deduplicated, and what the call returns (import set id or job id), all of which matter for an open-world mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence is front-loaded and free of padding, but the redundant write tag occupies part of an already minimal definition. Brevity here reflects under-specification rather than disciplined editing.

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?

For a non-idempotent, open-world import tool with no output schema, the definition says nothing about return values, error/partial-success behavior, or where the imported records end up. An agent would have to call it blind to learn the outcome contract.

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 the async/job-switching behavior and the table example, so the schema carries the parameter burden. The description adds no additional meaning about the shape of records in data or the target table beyond the schema.

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 (Import), resource (CI data into CMDB), and mechanism (import set), which is more than a restatement of the name. It does not explicitly distinguish itself from siblings like create_import_set_row or get_import_set, so an agent must infer the boundary.

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 or when-not-to-use guidance, and no alternative is named. The definition never says whether this creates a new import set, appends to an existing one, or when to prefer row-by-row creation via create_import_set_row.

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