Skip to main content
Glama
Sign In
drizzle-mcp

drizzle-mcp

by Fredobumma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Drizzle schema

schema
Read-only

Lists database tables in a Drizzle project by TypeScript or SQL name, and describes a selected table's columns, defaults, keys, indexes, checks, and relations.

Instructions

Lists the tables in the Drizzle schema with their TypeScript and SQL names, or with table, describes one: columns with types, nullability and defaults, keys, indexes, checks and relations.

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

Input Schema

NameRequiredDescriptionDefault
tableNoA table to describe: its TypeScript export or SQL name.

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. What the description adds is return-content detail (columns, types, nullability, defaults, keys, indexes, checks, relations), which is valuable given there is no output schema, though it says nothing about error behavior for unknown or ambiguous table names.

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 sentence carries the listing mode, the parameter-triggered mode, and the full field inventory of the described output. The primary behavior is front-loaded and nothing is redundant.

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 output schema, the description does the heavy lifting by enumerating exactly what a table description contains, which is sufficient for an agent to decide whether to call it. Minor gaps remain around the shape of the listing result and behavior for invalid table identifiers.

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 coverage is 100% and the single parameter already documents that it accepts a TypeScript export name or an SQL name. The description's 'or with `table`' restates the parameter's role rather than adding new meaning such as case sensitivity or handling of ambiguous names, so the baseline 3 applies.

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 names a specific verb ('Lists') and resource ('tables in the Drizzle schema') and explicitly covers both modes: a bare listing and a per-table description when `table` is supplied. It does not, however, distinguish itself from ambiguous siblings like `browse`, `explain`, or `drift`, which an agent must guess at.

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 by the branch condition: omit `table` to list, pass `table` to describe one. There is no explicit statement of when this tool is preferable to `browse`, `query`, or `explain`, nor any exclusion or prerequisite guidance.

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