Skip to main content
Glama

get_cmdb_data_foundations

Read-only

Retrieve ServiceNow CMDB and CSDM Data Foundations scores, failing-record counts, priorities, remediation playbook links, and drill-down tables to identify and fix data quality gaps.

Instructions

ServiceNow's own CMDB and CSDM Data Foundations scores (plugin com.snc.cmdb.getwell): each metric's result percent, failing record count, priority, CMDB tab or CSDM stage (Foundation, Crawl, Walk, Run, Fly) and the ServiceNow KB remediation playbook link, plus the drill-down tables (for example application services missing a business application, duplicate locations) with counts, list links and sample CIs. Read-only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cmdb_data_foundations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sample CIs per drill-down table (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the trailing 'Read-only' is redundant. Beyond that, the description earns credit by disclosing exactly what comes back: per-metric result percent, failing record count, priority, CMDB tab or CSDM stage, KB remediation link, plus drill-down tables with counts, list links and sample CIs. With no output schema, this return-shape disclosure is genuinely useful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single very long sentence stuffed with parenthetical enumerations (metric fields, CSDM stages, example drill-downs). The most important content leads, but the mid-sentence example list ('application services missing a business application, duplicate locations') is bulky and the trailing 'Read-only' is dead weight given the annotations.

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?

With no output schema, the description carries the return-value burden well, covering both the metric-level results and the drill-down tables. Gaps are minor: no mention of when scores are computed/refreshed or whether the plugin must be installed/licensed, which matters for a plugin-specific 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% and the single `limit` parameter is fully documented in the schema as 'Max sample CIs per drill-down table (default 5)'. The description corroborates the drill-down/sample-CI concept but adds no syntax or format detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a very specific resource: ServiceNow's own CMDB/CSDM Data Foundations scores from plugin com.snc.cmdb.getwell, and enumerates the metric fields and drill-down tables returned. That is far more concrete than a generic 'get health' tool, but there is no explicit verb and no direct contrast with siblings like cmdb_health_dashboard, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, so an agent cannot tell from the description whether this or cmdb_health_dashboard / analyze_data_quality is the right entry point. 'Read-only' is a safety property, not usage guidance.

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