servicenow-api

Ingest cmdb data

servicenow_ingest_cmdb_data

Inserts records into the Import Set table linked to a data source sys_id. Use it to ingest CMDB data from object arrays and return the ingestion result.

Instructions

Inserts records into the Import Set table associated with the data source.

:param data_source_sys_id: Sys_id of the data source record. :type data_source_sys_id: str :param records: Array of objects to ingest. :type records: list

:return: Response containing ingestion result. :rtype: Response

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

Input Schema

Name	Required	Description	Default
`data`	No
`records`	No
`data_source_sys_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Oct 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the mutation and non-idempotent nature is covered. The description adds little beyond this: it does not explain the staging/transient nature of import set tables, duplicate handling, or what a successful ingestion actually commits, and the ':return:' line is a boilerplate restatement.

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?

The docstring is short and the core purpose is front-loaded, but the :type:/:rtype: lines largely duplicate what the JSON schema already expresses as types, so some of the text does not earn its place. Formatting is the RST docstring convention rather than agent-oriented prose.

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?

A mutation tool with no output schema and 0% schema coverage needs the description to explain inputs and outcomes. It omits one parameter entirely and describes the return only as 'Response containing ingestion result', which tells an agent nothing about success/failure shape or whether records are staged versus committed.

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?

With 0% schema description coverage the description must carry the load. It documents two of three parameters meaningfully ('sys_id of the data source record', 'array of objects to ingest') but leaves the 'data' parameter entirely undocumented. Partial compensation for a fully undocumented 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 (inserts) and resource (Import Set table) with the additional qualifier that the table is that 'associated with the data source'. This is clear, but it does not differentiate itself from close siblings like servicenow_insert_import_set or servicenow_insert_multiple_import_sets, so an agent must guess which ingestion path to pick.

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 statement of when to use this tool versus servicenow_insert_import_set, servicenow_insert_multiple_import_sets, or servicenow_get_import_set. No prerequisites (e.g. the data source must already exist) or exclusion conditions are given, so usage must be inferred entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server