Skip to main content
Glama

Search CMDB Configuration Items

servicenow_search_ci
Read-onlyIdempotent

Search ServiceNow CMDB configuration items (CIs) by name, class, location, or custom filters. Retrieve details like status, assignment, and location.

Instructions

Search for ServiceNow CMDB configuration items (CIs) by name, type, location, or any filter.

Args:

  • query (string): Encoded query (e.g., 'nameLIKEweb-server', 'sys_class_name=cmdb_ci_server', 'location.name=Data Center'). Default: operational CIs.

  • class_name (string): Filter by CI class (e.g., 'cmdb_ci_server', 'cmdb_ci_database', 'cmdb_ci_application', 'cmdb_ci_network_adapter'). Leave empty to search all classes.

  • name_contains (string): Shortcut to filter by name contains

  • limit / offset: Pagination

  • response_format: Output format

Common class names:

  • cmdb_ci_server — Physical/virtual servers

  • cmdb_ci_computer — Workstations/laptops

  • cmdb_ci_app_server — Application servers

  • cmdb_ci_database — Database instances

  • cmdb_ci_web_server — Web servers

  • cmdb_ci_service — Business services

Returns: CI records with name, class, status, assignment, and location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1–100, default 20)
queryNoEncoded query (default: operational CIs)operational_status=1
offsetNoNumber of results to skip for pagination (default 0)
class_nameNoCI class name to filter (e.g., cmdb_ci_server)
name_containsNoFilter CIs where name contains this string
response_formatNoOutput format: 'markdown' (default) for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive. The description adds useful behavior: default query is operational CIs, it returns records with specific fields, and it documents pagination. This goes beyond annotations without contradicting them.

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 structured with an 'Args' section, common class names, and return info. It's longer than minimal, but every section adds value (examples, defaults, output details). The main summary is front-loaded and the extra details are logically ordered.

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?

With 6 parameters and no output schema, the description fully compensates: it explains every param, provides practical examples, lists common values, and states return content. For a search tool of this complexity, it is essentially complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description enhances semantics by giving concrete encoded query examples (e.g., 'nameLIKEweb-server'), listing common class names, and clarifying response_format options. This adds real meaning beyond 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 opens with 'Search for ServiceNow CMDB configuration items (CIs) by name, type, location, or any filter', clearly stating the verb (search), resource (CIs), and scope. This distinguishes it from siblings like servicenow_get_ci (retrieving a specific CI) and generic query tools.

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 gives clear search context: it supports name/type/location filters and lists common class names, implying it's for filtering searches. However, it doesn't explicitly mention alternatives or exclusion scenarios, only implicitly differentiating via the search posture.

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/kylburns89/servicenow-mcp-server'

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