Skip to main content
Glama
arpe-io

MigratorXpress MCP Server

by arpe-io

preview_command

Preview the exact database migration command that will be executed, preventing unintended changes by verifying parameters before running.

Instructions

Build and preview a MigratorXpress CLI command WITHOUT executing it. This shows the exact command that will be run. Use this FIRST before executing any command. License text is masked in the display output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_fileYesPath to authentication/credentials JSON file
source_db_auth_idYesSource database credential ID from the auth file
source_db_nameYesSource database name to migrate from
target_db_auth_idYesTarget database credential ID from the auth file
target_db_nameYesTarget database name to migrate to
migration_db_auth_idYesMigration tracking database credential ID from the auth file
source_schema_nameNoSource schema name. If omitted, all schemas are migrated
target_schema_nameNoTarget schema name. Defaults to source schema name if omitted
task_listNoTasks to run (e.g., translate, create, transfer, diff, copy_pk, copy_ak, copy_fk, all)
resumeNoResume a previous run by RUN_ID
fasttransfer_dir_pathNoPath to FastTransfer binary directory for parallel data transfer
fasttransfer_pNoFastTransfer parallel degree (number of threads per table transfer)
ft_large_table_thNoRow count threshold above which FastTransfer parallelism is used
n_jobsNoNumber of concurrent table transfers
cci_thresholdNoRow count threshold for clustered columnstore index creation on target
aci_thresholdNoRow count threshold for auto-created indexes on target
migration_db_modeNoMigration database mode: preserve (keep), truncate (clear data), drop (recreate)
compute_nbrowsNoCompute row counts for source tables before transfer
drop_tables_if_existsNoDrop target tables before creating them
load_modeNoData load mode: truncate (clear target first) or append
include_tablesNoTable include patterns, comma-separated. Supports wildcards
exclude_tablesNoTable exclude patterns, comma-separated. Supports wildcards
min_rowsNoMinimum row count filter — only migrate tables with at least this many rows
max_rowsNoMaximum row count filter — only migrate tables with at most this many rows
forced_int_id_prefixesNoColumn name prefixes to force integer identity mapping
forced_int_id_suffixesNoColumn name suffixes to force integer identity mapping
profiling_sample_pcNoPercentage of rows to sample for data profiling (0-100)
p_queryNoParallelism degree for profiling queries
min_sample_pc_profileNoMinimum sample percentage for profiling small tables
forceNoForce overwrite of existing migration data
basic_diffNoUse basic diff mode (row counts only, no checksum)
without_xidNoDisable transaction ID tracking during transfer
fk_modeNoForeign key mode: trusted, untrusted, or disabled
log_levelNoLogging verbosity level
log_dirNoDirectory for log files
no_bannerNoSuppress the startup banner
no_progressNoDisable progress bar display
quiet_ftNoSuppress FastTransfer console output during data transfer
licenseNoLicense key (will be masked in display)
license_fileNoPath to license key file
os_typeNoTarget operating system for command formattinglinux
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool does not execute and masks license text, but doesn't explicitly state there are no side effects or describe the output format.

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 three sentences, each adding value: purpose, output nature, usage order, and masking detail. No wasted words.

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

Completeness3/5

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

With 41 parameters and no output schema, the description lacks details on the preview output format (e.g., is it a string? formatted command?). Adequate but not complete.

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?

The schema has 100% description coverage, so the tool description adds no parameter-specific meaning beyond noting license masking. Baseline 3 is appropriate.

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 explicitly states 'Build and preview a MigratorXpress CLI command WITHOUT executing it' and 'Use this FIRST before executing any command', clearly differentiating it from its sibling execute_command.

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 description provides clear guidance to 'Use this FIRST before executing any command', implying its role as a preliminary step before execute_command, though it doesn't explicitly list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arpe-io/migratorxpress-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server