FrameIO MCP Server

generate_plugin_migration

Generate a database migration for a plugin by specifying version, description, and table definitions with columns and indexes.

Instructions

Generate a new database migration for a specific plugin with table definitions

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": {
      "pluginId": "<pluginId>",
      "version": "<version>",
      "description": "<description>",
      "tables": "<tables>"
    },
    "name": "generate_plugin_migration"
  }
}

Input Schema

Name	Required	Description
`tables`	Yes	Array of table definitions to create
`version`	Yes	Migration version (e.g., 1.1.0)
`pluginId`	Yes	Kebab-case plugin identifier (e.g., my-plugin)
`description`	Yes	Description of the migration (e.g., Add settings table)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 4, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Generate a new database migration' without revealing side effects (e.g., file creation, overwriting existing migrations, validation requirements), whether the plugin must already exist, or any idempotency guarantees. This is a significant gap for a generation tool.

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?

The description is a single, well-formed sentence with zero redundancy. It front-loads the core action and resource, and the qualifier is concise. Every word earns its place, making it highly efficient.

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

Completeness2/5

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

The tool has no output schema and no annotations, yet the description fails to mention what the tool returns or produces (e.g., a file path, a success message), or any prerequisites like plugin existence. For a generator with side effects, this is incomplete—an agent cannot anticipate the tool's behavior beyond the vague 'generate'.

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 description coverage is 100%, so all four parameters already have descriptions in the schema. The tool description itself adds no additional semantic detail beyond the schema, such as constraints or relationships. Baseline 3 is appropriate given the high coverage.

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 ('Generate'), a resource ('database migration'), and a qualifier ('for a specific plugin'), clearly distinguishing it from the sibling 'generate_migration' which likely targets general migrations. The mention of 'table definitions' further clarifies the scope. This is unambiguous and specific.

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?

The phrase 'for a specific plugin' provides clear context that this tool is intended when working with a plugin, implying a distinction from generic migration generation. However, it does not explicitly name the alternative (e.g., generate_migration) or state when not to use it. Thus, it has clear context but no explicit exclusions.

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