Skip to main content
Glama

db_inspect

Read-only

Inspect PostgreSQL and Odoo database schemas, list modules and tables, and compare before/after states to identify migration risks and promotion readiness.

Instructions

Introspect PostgreSQL & Odoo enterprise databases and compare schema states.

Actions:

  • 'list': Enumerate allowlisted target databases and active disposable rehearsal copies.

  • 'overview': Database size, largest tables, module counts, and problem indicators.

  • 'modules': List installed Odoo modules with version, status, and code existence.

  • 'table': Structure of one table: columns, data types, nullability, defaults, indexes.

  • 'compare': Diff before vs after databases with risk findings and promotion verdict.

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": {
      "action": "<action>"
    },
    "name": "db_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNoDatabase name (target or vmcp_ copy)
afterNoPost-migration database for compare
majorNoMajor version filter (e.g. '17')
stateNoModule state filter
tableNoTable name for action='table'
actionYes
beforeNoPre-migration database for compare
code_missingNoFilter modules missing code
exact_countsNoCompute exact table row counts in compare

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds useful scope detail — 'allowlisted target databases', 'disposable rehearsal copies', and that compare yields 'risk findings and promotion verdict' — but says nothing about permissions needed, cost of exact row counts, or latency. No contradiction with annotations.

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?

Front-loaded summary sentence followed by a tight five-bullet action list; every bullet describes a distinct capability with no filler. Slightly short of a 5 because the bullets describe returned content but not the parameter preconditions that matter for correct invocation.

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 nine parameters, only one required, and an output schema already documenting returns, the description covers the 'what' well. The real gap is per-action parameter binding: all the action-specific inputs (table, before, after, state, major, code_missing) are optional in the schema, so nothing warns an agent that action='table' without a table name or action='compare' without before/after will fail.

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?

Schema description coverage is 89%, so parameters are largely self-documenting and a baseline 3 applies. The description does implicitly map before/after to the compare action and table to action='table', but adds no format detail or constraint beyond the 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?

Starts with a specific verb and resource ('Introspect PostgreSQL & Odoo enterprise databases') and enumerates five distinct action modes with concrete outputs, so an agent knows exactly what the tool covers. It falls short of a 5 because it never contrasts itself with plausible overlap siblings such as migration_audit ('compare') or rehearsal_manage ('active disposable rehearsal copies').

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 action bullets implicitly tell the agent which mode serves which need ('structure of one table', 'diff before vs after databases'), which is more than none. However, there is no explicit when-not guidance, no routing to sibling tools, and no statement of which parameters each action requires (e.g. 'table' for action='table', before/after for action='compare').

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