Skip to main content
Glama
jschuller

ServiceNow MCP Server

by jschuller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Ci

list_ci
Read-onlyIdempotent

List CMDB configuration items with optional class and query filters to retrieve specific records from ServiceNow.

Instructions

List CMDB configuration items with optional class and query filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of CIs to return
queryNoEncoded query string (e.g., 'operational_status=1')
fieldsNoComma-separated list of fields to return
offsetNoNumber of records to skip
class_nameNoCMDB class name (e.g., 'cmdb_ci', 'cmdb_ci_server', 'cmdb_ci_computer')cmdb_ci

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv0.5.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. The description simply says 'List', which is consistent but adds no additional behavioral context. It does not contradict the annotations.

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?

The description is a single, concise sentence that directly conveys the tool's purpose without unnecessary detail or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation, the description is adequate. It doesn't specify return format, but the tool name and description imply a list of CIs. Since there is no output schema, this is not a critical omission, though a note on pagination could be helpful.

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?

The schema provides full descriptions for all five parameters (limit, query, fields, offset, class_name), covering 100% of the parameters. The description text does not add extra meaning beyond what the schema already conveys, so a baseline score is appropriate.

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 the tool's function: listing CMDB configuration items. It specifies the resource (CMDB configuration items) and the action (List), and mentions optional class and query filtering, which distinguishes it from generic list 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 implies usage for listing CIs with class or query filters, but does not explicitly state when to use it over alternatives like list_records. However, the mention of class and query filtering provides clear context for its specialized purpose.

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

Deploy Server

Other Tools