Scribase

migrate.run

Plan, lint, and optionally apply migrations. POST .../environments/{env}/migrations. migrations is a JSON array of {version,name,up,down?}. Without apply it only plans and lints; with apply true it applies and so requires confirm.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>",
      "migrations": "<migrations>",
      "confirm": "<confirm>"
    },
    "name": "migrate.run"
  }
}

Input Schema

Name	Required	Description
`apply`	No	Apply after the lint passes (default false)
`confirm`	Yes	Must be true to apply this mutation; otherwise the tool returns the request it would send for approval.
`migrations`	Yes	migrations (required)
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`organization_id`	Yes	organization_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description adds real value by explaining that the default is a non-mutating plan/lint pass and that mutation only occurs when apply is set and confirm satisfies the approval gate. It does not say what the lint output looks like or whether an applied migration is reversible, which keeps it below 5.

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?

Compact and front-loaded: capability, endpoint, payload shape, then the dry-run versus apply distinction. The telegraphic style is dense but each sentence carries information; only the endpoint fragment is arguably padding.

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?

For a mutating tool with no output schema, it covers the essentials an agent needs: the payload element shape, the safe default, and the confirm gate. Missing is any statement of what plan/lint results are returned or what failure looks like, which matters for a non-idempotent mutation.

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%, but the schema's own descriptions are bare restatements of parameter names, so the description's disclosure that migrations is a JSON array of {version,name,up,down?} is genuinely useful added meaning. It also creates mild confusion by describing apply as boolean-style 'apply true' while the schema types it as a string, and it adds nothing about the four ID parameters.

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?

Uses a specific verb triple (plan, lint, apply) on a specific resource (migrations) plus the concrete endpoint path, so the agent knows exactly what operation this is. It falls short of a 5 because it never distinguishes this hybrid plan/apply tool from the sibling migrations.apply and migrations.list tools, leaving overlap ambiguity.

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?

It does give a usable conditional: without apply it only plans and lints, with apply true it applies and requires confirm. However, it never says when to pick this tool versus the existing migrations.apply sibling, which is the most likely routing confusion for an agent.

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

All Scribase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?