db-autoconformite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_instancesA | List the database fleet from the inventory (CMDB): engine, environment, hosting, owner, and whether the instance is in the compliance perimeter (not cloud-native). |
| get_configA | Read the compliance-relevant configuration of one instance, in engine-neutral
terms, with any fact that could not be collected listed under |
| check_complianceA | Check one instance, or every in-scope instance ("all"), against the baseline. Returns each rule's status (pass / fail / unknown), severity, observed and expected values. UNKNOWN means the fact could not be read: it is never treated as compliant. |
| correlate_sourcesA | 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. |
| explain_ruleB | Explain a baseline rule: why it exists, where each engine (PostgreSQL, Oracle) exposes the fact, and the proposed fix. |
| propose_remediationA | Propose a remediation plan for one instance: failing rules most severe first, the engine's fix, and maintenance-window warnings. Nothing is executed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| baseline | The compliance baseline (YAML). |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: inventory listing, raw configuration reading, baseline compliance evaluation, cross-source reconciliation, rule explanation, and remediation planning. There is little risk of an agent confusing get_config with check_compliance or list_instances with correlate_sources because the descriptions sharply separate reading, evaluating, and reconciling.
All six tools use consistent snake_case with a verb_noun structure: list_instances, get_config, check_compliance, correlate_sources, explain_rule, propose_remediation. The convention is predictable and readable throughout.
Six tools is well-scoped for a database compliance auditing server: each tool covers a distinct stage of the workflow from inventory and configuration reading through checking, reconciliation, explanation, and remediation proposal. No tool appears redundant or arbitrarily included.
The surface covers the main compliance lifecycle well: inventory, configuration, checking, cross-source reconciliation, rule explanation, and remediation planning. A minor gap is the absence of a tool to list available baseline rules or rule IDs, which would help agents discover what can be passed to explain_rule; execution of remediation is intentionally out of scope.