Skip to main content
Glama
ketiil

ServiceNow CMDB MCP Server

by ketiil

get_ci_details

Read-onlyIdempotent

Retrieve complete details of a configuration item using its sys_id. Specify fields to get only needed attributes, or receive a broad default set including common CI fields.

Instructions

Get the full details of a single configuration item by its sys_id.

Returns all requested fields for the CI. If no fields are specified, returns a broad set of common CI attributes. Use this tool when you need complete information about a specific CI, such as after finding it via search_cis.

Prerequisites: Use search_cis or query_cis_raw to find the sys_id first. This tool only accepts sys_id (a 32-character hex identifier), not CI names. To look up a CI by name: search_cis(name_filter="my-server") → use the returned sys_id.

Examples: get_ci_details(sys_id="abc123...", table="cmdb_ci_server") get_ci_details(sys_id="abc123...", table="cmdb_ci_linux_server", display_value="true") get_ci_details(sys_id="abc123...", fields=["name", "ip_address", "os", "os_version"])

Args: sys_id: The 32-character sys_id of the CI record (from search_cis or query_cis_raw). table: The CMDB table the CI belongs to (e.g. cmdb_ci_server). Defaults to cmdb_ci. Using the specific class table is more efficient and returns class-specific fields. fields: Specific fields to return. If omitted, returns a broad default set including sys_id, name, sys_class_name, asset_tag, serial_number, ip_address, operational_status, install_status, location, department, company, os, os_version, cpu_count, ram, disk_space, discovery_source, first_discovered, last_discovered, sys_created_on, sys_updated_on. display_value: Controls how reference fields (location, company, assigned_to, etc.) are returned. "" (default) returns raw sys_id values. "true" returns human-readable display values (e.g. "New York" instead of a sys_id). "all" returns both as {"value": sys_id, "display_value": "New York"}. Use "true" when presenting data to users; use "all" when you need both the sys_id (for API calls) and the display name.

Returns: JSON object with the CI record fields, plus a "url" field linking to the ServiceNow record, or a NotFoundError if the sys_id does not exist. When display_value="all", each reference field is returned as {"value": sys_id, "display_value": label} instead of a plain sys_id string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sys_idYes
tableNocmdb_ci
fieldsNo
display_valueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description is consistent with annotations (readOnlyHint, destructiveHint false, idempotentHint). It adds context about default field behavior, display_value options, and error handling (NotFoundError for non-existent sys_id). No contradictions with annotations.

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?

Well-structured with clear sections (purpose, prerequisites, examples, arguments, returns). Front-loaded with core purpose. However, the default fields list is quite lengthy; while informative, it makes the description somewhat verbose. Still excellent overall.

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 4 parameters (1 required) with detailed descriptions, and an output schema (present but not shown), the description covers all parameter behaviors, return value structure, and error case. It fully equips an agent to use the tool correctly.

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 coverage is 0%, so description carries full burden. It explains each parameter: sys_id (32-character hex), table (with default and efficiency tip), fields (default broad set listed), display_value (three modes with examples). Adds significant meaning beyond the raw 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?

The description clearly states 'Get the full details of a single configuration item by its sys_id', specifying the verb, resource, and key identifier. It distinguishes itself from sibling tools like search_cis (which finds CIs) and query_cis_raw (which may have different querying capabilities).

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 when to use: 'when you need complete information about a specific CI, such as after finding it via search_cis'. Provides prerequisites (use search_cis or query_cis_raw to find sys_id), and explains that it only accepts sys_id (not CI names), with an example of how to look up by name.

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