Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

correlate_sources

Read-onlyIdempotent

Cross-checks CMDB inventory, network discovery and collected facts to flag uninventoried responders, unreachable or unreadable inventoried instances, missing owners, and out-of-scope assets.

Instructions

Cross the inventory (CMDB), network discovery and the collected facts: instances that answer but are not inventoried, inventoried ones that do not answer or cannot be read, missing owners, and what is out of scope.

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": "correlate_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful detail about the discrepancy categories detected, but it does not describe execution behavior such as data freshness, permissions, or response format.

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

Conciseness4/5

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

The description is a single, front-loaded sentence that efficiently names the sources and then enumerates the discrepancy categories. It is appropriately sized, though the phrasing is somewhat dense and terse.

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?

For a zero-parameter analytical tool with no output schema, the description gives enough context to understand what the tool compares and what categories of findings it surfaces. It could say more about the return structure, but the core invocation context is complete.

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?

The tool has zero parameters and 100% schema coverage, so there are no parameter semantics to clarify. The baseline score for a parameterless tool is 4.

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 uses a specific verb, 'Cross,' and names the three sources being reconciled: CMDB inventory, network discovery, and collected facts. It also lists the kinds of discrepancies found, making the tool's purpose clear, though it does not explicitly differentiate itself from siblings such as list_instances or check_compliance.

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?

Usage is implied by the description of cross-source reconciliation, but there is no explicit guidance on when to choose this tool over alternatives like list_instances or check_compliance. No exclusions or prerequisites are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.