Skip to main content
Glama
jschuller

ServiceNow MCP Server

by jschuller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Ci Relationships

get_ci_relationships
Read-onlyIdempotent

Retrieve parent and child relationships for a specific CMDB configuration item using its sys_id, with optional relation type filter and pagination.

Instructions

Get relationships for a CMDB configuration item (parent and child)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of relationships to return
offsetNoNumber of relationships to skip
sys_idYesThe sys_id of the CI
relation_typeNoFilter by relationship type sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum number of relationships to return",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of relationships to skip",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv0.5.1

TDQS

A3.8/5.0
Behavior3/5

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

The description is consistent with the annotations (readOnlyHint, idempotentHint, destructiveHint=false). It does not add extra behavioral detail beyond the annotations, but no contradiction exists, so it meets the baseline.

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 with no redundant information. It efficiently captures the tool's purpose without extraneous detail.

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?

While there is no output schema, the description gives context by mentioning 'parent and child', which helps understand the nature of the returned relationships. It is mostly complete for a straightforward get operation, though it does not specify the exact response format.

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?

All parameters (sys_id, relation_type, limit, offset) have descriptions in the schema, providing full coverage. The description does not add additional semantic meaning beyond what the schema already provides.

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 retrieves relationships for a CMDB configuration item, specifying both parent and child relationships. It is distinct from sibling tools like get_ci (which fetches a single CI) and list_ci (which lists CIs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the basic function but does not explicitly state when to use this tool over alternatives (e.g., when to use get_ci_relationships vs list_ci). It implies usage for relationship data but lacks explicit guidance on selection criteria.

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