Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

check_compliance

Read-onlyIdempotent

Audit one PostgreSQL or Oracle instance, or all in-scope instances, against a compliance baseline and return pass, fail, or unknown status per rule with severity, observed, and expected values.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
instanceNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds valuable behavioral detail by explaining that results include pass/fail/unknown status, severity, observed and expected values, and that UNKNOWN is never treated as compliant.

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?

The description is only a few sentences, front-loads the scope and purpose, and then adds return-value and UNKNOWN semantics. Every sentence contributes useful information.

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?

For a simple one-parameter read-only tool with no output schema, the description covers scope, return fields, status meanings, and the important UNKNOWN rule. It gives enough context for an agent to call and interpret the tool without needing more.

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 description coverage is 0%, so the description must carry parameter meaning. It meaningfully explains that the optional instance parameter accepts one instance or the special value "all", though it does not specify the expected identifier format for individual instances.

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 clear verb-resource pairing: check instances against a compliance baseline. It is more specific than the name alone, but it does not explicitly differentiate its role from siblings such as explain_rule or propose_remediation.

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?

It indicates that the tool can check one instance or all in-scope instances, which gives scope guidance. However, it does not state when to use this tool instead of related tools like explain_rule or get_config, nor does it give exclusions or prerequisites.

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