Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

get_config

Read-onlyIdempotent

Reads the compliance-relevant configuration of one database instance in engine-neutral terms, listing any facts that could not be collected under missing.

Instructions

Read the compliance-relevant configuration of one instance, in engine-neutral terms, with any fact that could not be collected listed under missing.

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": {
      "instance": "<instance>"
    },
    "name": "get_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description earns credit for disclosing a genuine behavioral trait beyond annotations: partial collection is not an error, and uncollected facts surface under a `missing` field. It stops short of describing the overall return structure.

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?

A single front-loaded sentence with no filler; the scope, the normalization guarantee, and the `missing` caveat all arrive in one pass.

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 one-parameter read tool with no output schema, the definition covers what is fetched, how it is normalized, and how gaps are reported. The remaining gap is the identifier format expected for `instance`, which an agent needs in order to call it correctly.

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?

With one parameter and 0% schema description coverage, the description must carry the parameter's meaning. "One instance" confirms the parameter selects a single target, but neither the accepted identifier format (ID vs. name) nor any constraint is given, so the compensation is only partial.

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?

"Read the compliance-relevant configuration of one instance" gives a specific verb and a scoped resource, and "engine-neutral terms" signals the output is normalized rather than raw. It is distinguishable from siblings like check_compliance (evaluation) and list_instances (enumeration), though the description never says so explicitly.

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: "one instance" suggests fetching config for an already-known instance, but there is no statement of when to prefer this over check_compliance or how an instance is chosen. No exclusions or alternatives are named.

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