Skip to main content
Glama
db-autoconformite-mcp

db-autoconformite-mcp

list_instances

Read-onlyIdempotent

Retrieve the database fleet from CMDB inventory—engine, environment, hosting, owner, and compliance-perimeter status—to identify which instances are in scope for compliance auditing.

Instructions

List the database fleet from the inventory (CMDB): engine, environment, hosting, owner, and whether the instance is in the compliance perimeter (not cloud-native).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 fully covered without the description. The description adds genuine context beyond that: the data comes from a CMDB inventory rather than a live scan, and the parenthetical clarifies what the compliance-perimeter field means. It does not disclose freshness/staleness of the inventory data or the result volume, which are the traits an agent would still need.

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 action and data source come first, followed by the fields produced. Every clause carries information, including the parenthetical disambiguation.

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?

With no output schema, the description must carry the return-value burden, and it does partially by naming the fields returned. For a zero-parameter listing tool it is nearly sufficient, but it omits whether the whole fleet is returned in one call, roughly how large that is, and how current the CMDB snapshot is — all relevant given there is no pagination parameter to control.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description instead spends its words on the shape of the returned record, which is the useful information for a no-argument tool.

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 ("List") plus a specific resource ("the database fleet from the inventory (CMDB)") and enumerates the returned attributes: engine, environment, hosting, owner, compliance-perimeter flag. That is enough to separate it from a single-resource reader like get_config, but it never explicitly contrasts itself with check_compliance, which the mention of "compliance perimeter" could make an agent confuse with a compliance check.

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 can infer this is the enumeration entry point for the fleet inventory, which precedes per-instance lookups. There is no statement of when to prefer it over check_compliance or correlate_sources, and no guidance on what to do after listing (e.g. feed names into get_config).

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