Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

propose_remediation

Read-onlyIdempotent

Generates a prioritized remediation plan for a single database instance, ordering failing rules by severity, including engine fixes and maintenance-window warnings; no changes are executed.

Instructions

Propose a remediation plan for one instance: failing rules most severe first, the engine's fix, and maintenance-window warnings. Nothing is executed.

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

Input Schema

NameRequiredDescriptionDefault
instanceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare the tool is read-only, idempotent, non-destructive, and closed-world. The description adds valuable behavioral context by emphasizing 'Nothing is executed' and by describing how the plan is ordered and what warnings it includes. It does not cover authorization, rate limits, or return format, but those are less critical given the annotations and the presence of an output schema.

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 definition is a single, front-loaded sentence with no wasted wording. It states the action, the scope, the plan contents, and the key non-execution guarantee efficiently.

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?

The tool is simple to invoke with one parameter, annotations already cover its safety profile, and an output schema exists to describe the returned plan. The description sufficiently explains what the tool does and that nothing is executed. The main remaining gap is the lack of guidance on the instance identifier format, which is minor given the schema.

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 for the single required parameter is 0%, so the description must compensate. It only says 'for one instance,' which largely restates the parameter name and does not explain whether the instance is an ID, a name, or where to obtain it. The description adds little meaningful semantics beyond the schema's type and required status.

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 gives a specific verb and resource: proposing a remediation plan for one instance. It also explains what the plan contains (failing rules ordered by severity, the engine's fix, maintenance-window warnings), making the purpose clear. It does not explicitly distinguish this tool from siblings such as check_compliance or explain_rule, so it falls short of a 5.

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?

The description implies usage by saying it proposes a plan for one instance and that nothing is executed. However, it gives no explicit guidance on when to choose this tool over alternatives such as check_compliance, explain_rule, or list_instances. The context is adequate but leaves the agent to infer the selection criteria.

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