Skip to main content
Glama
ketiil

ServiceNow CMDB MCP Server

by ketiil

get_ci_relationships

Read-onlyIdempotent

Return upstream (dependencies) and downstream (dependents) relationships for a configuration item, with details on each related CI's name, class, and operational status.

Instructions

Get all relationships for a configuration item.

Returns upstream (CIs this CI depends on), downstream (CIs that depend on this CI), or both. Each relationship includes the related CI's name, class, and operational status, plus the relationship type descriptor.

In ServiceNow CMDB relationships:

  • Upstream: this CI is the CHILD in the relationship (e.g., "Runs on" a server)

  • Downstream: this CI is the PARENT (e.g., a server that other CIs "Run on")

Prerequisites: Use search_cis to find the CI 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_relationships(ci_sys_id="abc123...", direction="downstream", limit=10) get_ci_relationships(ci_sys_id="abc123...", direction="upstream") get_ci_relationships(ci_sys_id="abc123...", direction="both", limit=50)

Args: ci_sys_id: The 32-character sys_id of the CI (from search_cis or query_cis_raw). direction: Which relationships to return: "upstream", "downstream", or "both". Defaults to "both". limit: Maximum relationships to return per direction (1-1000, default 25). offset: Pagination offset.

Returns: JSON object with "ci_sys_id", "direction", "count", and "relationships" list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ci_sys_idYes
directionNoboth
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnly, non-destructive, idempotent. The description adds meaningful context: upstream/downstream CMDB model, pagination details, and return structure. No contradictions.

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 sections, examples, and parameter list. Every sentence adds value, though slightly lengthy. Information is front-loaded.

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?

Complete for a read-only query tool: explains prerequisites, parameters, direction semantics, pagination, and return format. Output schema exists, but description adds practical context. Distinguishable from siblings.

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?

Despite 0% schema coverage, the description thoroughly explains all parameters: ci_sys_id (32-char hex from search_cis), direction (enum with defaults), limit (range 1-1000), offset (pagination). Adds semantic meaning beyond 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 the tool gets all relationships for a configuration item, specifies upstream/downstream/both, and lists included fields. It distinguishes from siblings by focusing on relationships and referencing search_cis for name lookup.

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 (use search_cis for sys_id), explains direction terminology, provides examples, and warns against using CI names directly. This fully guides when and how to use the tool.

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