Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Traverse CMDB Graph

traverse_cmdb_graph

Traverse the CMDB relationship graph from a Configuration Item to discover dependencies for impact analysis and service mapping. Supports directional and depth-limited exploration up to 5 levels.

Instructions

Traverse the CMDB relationship graph starting from a Configuration Item using breadth-first search. Returns all nodes (CIs) and edges (relationships) discovered up to the specified depth.

Use this for deep impact analysis, service mapping, and understanding the full dependency chain of a CI. Max depth is 5, max nodes is 1000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
ci_sys_idYesThe sys_id of the root Configuration Item to start traversal from.
directionNoTraversal direction: "upstream", "downstream", or "both". Default is "both".both
max_depthNoMaximum traversal depth (1-5). Higher depth discovers more of the graph but makes more API calls. Default is 2.
relation_typeNoFilter traversal to only follow this relationship type.
max_nodesNoMaximum number of nodes to visit. Traversal stops when this limit is reached. Default is 200, max is 1000.
Behavior4/5

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

No annotations provided, but description honestly describes BFS traversal, return type, depth and node limits, and that it makes API calls. Does not mention side effects, but read-only nature is implied.

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?

Three sentences: action+algorithm+output, use cases, limits. No wasted words, front-loaded with key info.

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?

No output schema, but description explains return format (nodes and edges) and constraints. Lacks details on return structure, but sufficient for a traversal tool.

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?

Schema coverage is 100%; description adds no new parameter meaning beyond what's already in the schema. Baseline for high coverage is 3.

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 it traverses the CMDB graph using BFS starting from a CI, returning nodes and edges. This distinctly differentiates it from sibling 'get_cmdb_relationships' which likely returns only direct relationships.

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?

Explicitly states use cases: deep impact analysis, service mapping, dependency chain. Does not mention when not to use, but the use cases are clear and actionable.

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/sonisoft-cnanda/now-sdk-ext-mcp'

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