Skip to main content
Glama

Get schema migrations

get_schema_migrations
Read-onlyIdempotent

Retrieve recent Drizzle schema migrations from the Studio database as JSON to track schema history. Filter by workspace, set a row limit, and review recent changes.

Instructions

Show recent Drizzle schema migrations from the Studio database. Use get_msty_installation for the app version. Read-only. Returns JSON migrations.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows. Integer from 1 to 100. Default 20.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 100. Default 20."
  3. Addedv6.1.5

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read-only' merely restates structured data. The genuinely added context is the data source (Studio database) and that results are 'recent' migrations in JSON, but the JSON note duplicates the existing output schema.

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?

Four short, front-loaded sentences with no padding and the alternative route placed early. The 'Read-only.' sentence is redundant against the annotations and could be dropped without loss.

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 rich annotations, a 100%-documented two-parameter schema, and an output schema covering return values, the description supplies everything needed to call it correctly. Only ordering/pagination nuance of 'recent' is left implicit.

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%, with limit and workspace fully documented including defaults and the list_workspaces reference. The description contributes only the 'recent' ordering implication, which is a marginal add beyond the 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?

The description states a specific verb and resource: 'Show recent Drizzle schema migrations from the Studio database.' It also names the sibling tool get_msty_installation for a closely related need, so an agent can distinguish the two without inspecting either 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 explicitly routes the agent to get_msty_installation when the app version is what's wanted, and 'recent' signals the intended default view. It does not state exclusion cases (e.g. historical or filtered queries), which keeps it short of a 5.

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