Skip to main content
Glama

get_csdm_health

Read-only

Retrieves CSDM 5 health by domain as 0–100 scores with links and gap samples, so you can identify weak lifecycle, relationship, and CMDB policy areas.

Instructions

CSDM 5 health by domain, with a 0 to 100 score each and links: Design (business applications, product models), Build and integration, Service delivery (service instances, formerly application services, and technical services), Service consumption (business services, offerings), Foundation, life cycle stage adoption (life_cycle_stage vs legacy status, migration properties), relationships, CMDB data management and certification policies, and AI and MCP 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_csdm_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sample records per gap list (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' in the description earns no credit. What does add value is the disclosure of what the report contains (per-domain 0-100 scores plus links) since no output schema exists. It stops short of explaining pagination, sampling behavior, or how the undocumented 'gap list' interacts with the result.

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?

The purpose is front-loaded, which is good, but the middle is a run-on enumeration of CSDM domains with parenthetical asides and a jarring 'and links:' fragment that is grammatically ambiguous. The domain list conveys real scope, but it is not structured and the 'formerly application services' aside is legacy trivia.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description should carry the return-value burden, and it partially does by enumerating report sections. It does not explain the shape of the response (per-domain objects, score semantics, what 'links' means) or the gap-list sampling behavior implied by the parameter, leaving real gaps.

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?

There is a single optional parameter ('limit') and schema coverage is 100%, with the schema describing it as 'Max sample records per gap list (default 10)'. The description adds nothing about the limit or about the 'gap list' concept it references, so the baseline 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 concrete resource and scope: CSDM 5 health broken out by domain with 0-100 scores and links. It is not a tautology and an agent knows it returns a scored health report rather than raw CIs. However, it never distinguishes itself from close siblings like cmdb_health_dashboard or service_health, which share the 'health' theme.

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 routing to alternatives such as cmdb_health_dashboard for general CMDB health. The only usage signal is the trailing 'Read-only', which repeats the readOnlyHint annotation rather than telling the agent when this report is the right pick.

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