Skip to main content
Glama
Sign In
drizzle-mcp

drizzle-mcp

by Fredobumma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare schema and database

drift
Read-only

Compares the Drizzle schema against the live database to reveal tables and columns that exist on only one side, plus type or nullability mismatches. Use it after schema changes or when queries fail on columns your code expects.

Instructions

Compares the Drizzle schema with the live database: tables and columns on one side only, and columns whose type or nullability differ. Use it when queries fail on columns the code expects, or after changing the schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/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 structurally. The description adds value beyond that by specifying the comparison axes (side-only objects, type/nullability mismatches), which tells the agent what the report is made of. It does not spell out that the live database must be reachable or how results are ordered, which keeps it short of a 5.

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?

Two sentences, no filler: the first defines the comparison and its outputs, the second defines when to reach for it. The core purpose is front-loaded before the usage hint.

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?

With no parameters, no nested objects, and a small surface, the description covers what the tool does and when to call it. Because there is no output schema, it could have gone slightly further in describing how the drift report is returned (grouped per table, diff format), which is the only remaining gap.

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 for the description to carry and the baseline of 4 applies. Nothing in the description contradicts or misdescribes the empty input schema.

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?

A specific verb ("Compares") plus two precisely named resources ("Drizzle schema" vs "live database"), followed by an enumeration of the exact discrepancy classes it reports: tables/columns present on one side only and columns whose type or nullability differ. That is enough to distinguish it from siblings like schema, migrations, and browse without opening any schema.

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

Usage Guidelines4/5

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

It gives two concrete triggering situations: queries failing on columns the code expects, and after changing the schema. What is missing is a negative case or a pointer to the sibling that fixes the problem (migrations) once drift is found, so the agent must infer the follow-up.

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

Deploy Server

Other Tools