Skip to main content
Glama
ketiil

ServiceNow CMDB MCP Server

by ketiil

preview_ci_create

Read-onlyIdempotent

Validates and returns a confirmation token for a new CI entry without inserting it into ServiceNow.

Instructions

Preview the creation of a new CI before inserting it.

Validates the fields and returns a confirmation token. No record is created in ServiceNow until confirm_ci_create is called.

The confirmation token is valid for 5 minutes.

Prerequisites: Call describe_ci_class(table) first to review mandatory fields and valid values before composing the fields dict. Call suggest_table if you are unsure of the correct table name.

Typical workflow: suggest_table → describe_ci_class → preview_ci_create → confirm_ci_create

Examples: preview_ci_create(table="cmdb_ci_server", fields={ "name": "web-server-01", "ip_address": "10.0.1.5", "operational_status": "1", "os": "Linux Red Hat" }) preview_ci_create(table="cmdb_ci_appl", fields={ "name": "MyApp", "operational_status": "1" }) preview_ci_create(table="cmdb_ci_linux_server", fields={ "name": "db-primary-01", "ip_address": "10.10.5.20", "os": "Linux Red Hat", "install_status": "1", "operational_status": "1" })

Args: table: The CMDB table to create the CI in (e.g. cmdb_ci_server). fields: Dictionary of field names to values. Must include at minimum a "name" field. Example: {"name": "web-server-01", "ip_address": "10.0.1.5", "operational_status": "1"}. System fields (sys_id, sys_created_on, etc.) cannot be set.

Returns: JSON object with "token" (confirmation token), "table", "fields" (the values to be created), and a human-readable message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYes
fieldsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Description adds valuable context beyond annotations: token validity (5 minutes), that no record is created, validation occurs. Does not contradict annotations (readOnlyHint, idempotentHint are consistent).

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

Conciseness5/5

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

Well-organized: purpose, behavior, prerequisites, workflow, examples, parameter docs. Front-loaded with main action. No superfluous sentences; each section earns its place.

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?

Given complexity (2 params, 0% schema coverage, output schema exists), description covers everything: prerequisites, workflow, return format (token, table, fields, message), usage constraints. No gaps.

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

Parameters5/5

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

Schema has 0% description coverage, but description fully explains each parameter: table (CMDB table name), fields (must include 'name', examples, cannot set system fields). This provides critical meaning absent from 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?

Clearly states it's a preview (what: preview CI creation) with specific verb 'Preview' and resource 'creation of a new CI'. Distinguishes from sibling tools like confirm_ci_create by noting it does not create a record and returns a token.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (call describe_ci_class first, suggest_table if unsure), provides a full typical workflow, and includes multiple examples. Clearly differentiates from confirm_ci_create by explaining the process order.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ketiil/mcp-cmdb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server