Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

explain_rule

Read-onlyIdempotent

Explains a compliance baseline rule: why it exists, where PostgreSQL and Oracle expose the fact, and the proposed fix, so you can validate remediation before applying it.

Instructions

Explain a baseline rule: why it exists, where each engine (PostgreSQL, Oracle) exposes the fact, and the proposed fix.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rule_id": "<rule_id>"
    },
    "name": "explain_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful content-level context by disclosing what the answer contains (rationale, where each of two engines surfaces the fact, and the proposed fix), which is information the annotations cannot convey.

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?

A single compact sentence with no filler, and the key noun (baseline rule) is front-loaded. The phrase 'where each engine exposes the fact' is slightly compressed but still parses as engine-specific data locations.

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 one-parameter read-only tool with no output schema, the description adequately frames what comes back, so no return-value documentation is required. The remaining hole is the input side: an agent cannot tell how to source a valid rule_id, which is the only failure mode this tool has.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, and the description says nothing about rule_id — not its format, not whether it comes from check_compliance output or list_instances. With only one required parameter, a brief note on where to obtain the identifier would have closed the gap entirely; as written the description does not compensate for the undocumented schema.

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?

States a specific verb (explain) and resource (a baseline rule), and enumerates the three things the explanation covers: rationale, per-engine (PostgreSQL, Oracle) exposure location, and the proposed fix. That is enough for an agent to tell it apart from list_instances or check_compliance, though it never explicitly names a sibling.

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 only implied: an agent should call this when it needs to understand a specific rule's background. There is no statement of when not to use it, no prerequisite (e.g., that a rule_id must first be discovered elsewhere), and no pointer to propose_remediation as the action counterpart to this explanatory tool.

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