Skip to main content
Glama
ketiil

ServiceNow CMDB MCP Server

by ketiil

search_cis

Read-onlyIdempotent

Search CMDB configuration items using structured filters. Filter by name, class, operational status, location, or OS. Returns paginated results with configurable fields and display values.

Instructions

Search CMDB configuration items with structured filters.

Builds an encoded query from the provided parameters and returns matching CIs. Name filtering uses STARTSWITH by default for performance (indexed operation).

Examples: search_cis(ci_class="cmdb_ci_linux_server", operational_status="1") search_cis(ci_class="cmdb_ci_win_server", name_filter="prod", display_value="true") search_cis(ci_class="cmdb_ci_server", location="New York", limit=50) search_cis(ci_class="cmdb_ci_server", display_value="all") # both sys_id and display name per reference field

Typical workflow: suggest_table → search_cis → get_ci_details → get_ci_relationships

Args: ci_class: CMDB table/class to query (e.g. cmdb_ci_server, cmdb_ci_linux_server). Defaults to cmdb_ci (all CI types). name_filter: Filter CIs whose name starts with this value. Leave empty for no name filter. operational_status: Filter by operational status numeric code. Valid values: "1" = Operational, "2" = Non-Operational, "3" = Repair in Progress, "4" = DR Standby, "5" = Ready, "6" = Retired, "7" = Pipeline, "8" = Catalog. os_filter: Filter by operating system (STARTSWITH match on the os field). location: Filter by location display value (STARTSWITH match). limit: Maximum number of results to return (1-1000, default 25). offset: Pagination offset for retrieving subsequent pages of results. fields: Specific fields to return. Defaults to sys_id, name, sys_class_name, operational_status, ip_address, location, 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 "count" (results on this page), "records" (list of CI dicts), "total_count", "has_more", "next_offset", and "suggested_next". When display_value="all", each reference field in a record is returned as {"value": sys_id, "display_value": label} instead of a plain sys_id string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ci_classNocmdb_ci
name_filterNo
operational_statusNo
os_filterNo
locationNo
limitNo
offsetNo
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 adds significant behavioral context beyond the annotations (readOnlyHint, destructiveHint, idempotentHint): it explains name filtering uses STARTSWITH for performance, pagination details (next_offset, has_more), return format (count, records, total_count), and display_value behavior (raw vs display vs both). 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?

The description is well-structured with a summary, examples, parameter list, and return section. It is somewhat lengthy but all information is relevant and front-loaded. A minor improvement could be tightening the parameter descriptions.

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 9 parameters, an output schema, and the tool's complexity, the description covers all necessary details: parameters, return format, display options, and pagination. It is self-contained and enables correct invocation without needing additional context.

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 description coverage is 0%, so the description fully compensates by documenting all 9 parameters with defaults, valid values (operational_status codes explained), behavior (name_filter STARTSWITH, limit range 1-1000), and detailed display_value explanation with examples. This adds substantial meaning 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?

The description clearly states the tool searches CMDB configuration items with structured filters, building an encoded query. The typical workflow differentiates it from other CI tools like get_ci_details, but does not explicitly contrast with similar search tools like query_cis_raw or count_cis.

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?

The description provides a typical workflow (suggest_table → search_cis → get_ci_details → get_ci_relationships) and examples, giving clear context for when to use this tool. However, it does not explicitly state when not to use it or name alternatives.

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