Skip to main content
Glama
clidey

whodb-cli

Official

whodb_diff

Read-onlyIdempotent

Compare schema metadata between two database connections to identify drift across environments like staging and production. Returns structured diff of storage units, columns, and relationships.

Instructions

Compare schema metadata between two database connections.

Best for: Spotting drift between environments; comparing staging vs production; reviewing storage-unit, column, and relationship changes. Not recommended for: Row-level data comparison. Common mistakes: Forgetting to specify both connections; comparing the same connection and schema without overrides.

Usage Example:

{
  "name": "whodb_diff",
  "arguments": {
    "from_connection": "staging",
    "to_connection": "prod",
    "from_schema": "public",
    "to_schema": "public"
  }
}

Returns: A structured schema diff with storage-unit, column, and relationship summaries plus per-object changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_connectionYesSource connection name
to_connectionYesTarget connection name
from_schemaNoSource schema override
to_schemaNoTarget schema override

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo
errorNo
request_idNo
Behavior5/5

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

Annotations (readOnlyHint: true, idempotentHint: true) align with description's read-only comparison. Description adds context on return structure ('storage-unit, column, and relationship summaries'), which is beyond annotations. No contradictions.

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?

Well-organized with sections, code block, and clear returns statement. Every sentence is informative; no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all needed information for a tool that compares schemas: purpose, when/not to use, common mistakes, parameter usage example, and return description. Output schema exists, so return description is sufficient.

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?

Schema coverage is 100%, so baseline is 3. Description adds value by showing a concrete usage example with each parameter and noting that from_schema/to_schema are overrides, which clarifies optionality beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states 'Compare schema metadata between two database connections', with 'Best for' section and usage example, clearly distinguishing from sibling tools like whodb_tables or whodb_columns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes 'Best for', 'Not recommended for', and 'Common mistakes' sections, providing explicit guidance on when to use (drift detection) and when not (row-level comparison), along with pitfalls like forgetting to specify both connections.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clidey/whodb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server