Skip to main content
Glama
ketiil

ServiceNow CMDB MCP Server

by ketiil

suggest_table

Read-onlyIdempotent

Find the appropriate CMDB table for a configuration item by describing it in natural language. Returns ranked suggestions with confidence scores to help identify the best match.

Instructions

Suggest the best CMDB table to query based on a natural language description.

Given a description like "linux servers", "network switches", "web applications", or "load balancers", this tool searches the CMDB class hierarchy to find the most appropriate table. It queries sys_db_object and sys_documentation for class labels and descriptions to find the best match.

Use this tool when you're unsure which CMDB table to query for a particular type of configuration item.

Each suggestion includes a confidence score (0-100) indicating how well it matches the description. When a single result clearly dominates, it is marked as best_match.

Examples: suggest_table(description="linux servers") → cmdb_ci_linux_server suggest_table(description="network switches") → cmdb_ci_netgear suggest_table(description="web applications") → cmdb_ci_appl Vague descriptions like "stuff" or "things" will return low-confidence matches.

Args: description: Natural language description of what you're looking for. Examples: "linux servers", "network switches", "web applications", "database instances", "storage devices", "virtual machines". limit: Maximum number of suggestions to return (1-1000, default 10). offset: Pagination offset for retrieving subsequent pages of suggestions.

Returns: JSON object with "suggestions" — a ranked list of matching CMDB tables with their name, label, confidence score, and pagination metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds: queries specific tables, returns confidence scores, best_match flag, pagination. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured: summary, details, usage guidance, examples, args. Approximately 200 words, front-loaded with purpose. Every sentence adds value.

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?

Given output schema exists, description covers purpose, when to use, behavior, parameters, return format (JSON with suggestions, confidence, best_match). Complete for the tool's functionality.

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 has 3 params with 0% description coverage. Description explains description with examples, limit (1-1000), offset (pagination). Could be more explicit about offset usage, but adds significant value.

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?

Description clearly states the tool suggests CMDB tables based on natural language. It uses specific verb 'suggest' and resource 'CMDB table', and distinguishes from sibling tools that query CIs or manage configurations.

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 says when to use: when unsure which CMDB table to query. Includes examples and notes about vague descriptions. Could mention alternatives for known tables, but overall clear.

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