Skip to main content
Glama
arpe-io

arpeio-mcp

Official
by arpe-io

migratorxpress_preview_command

Read-onlyIdempotent

Build and preview a MigratorXpress migration command without executing it. Displays the exact CLI command with passwords masked for review before execution.

Instructions

Build and preview a MigratorXpress migration command WITHOUT executing it. Shows the exact CLI command with passwords masked. Does NOT execute the migration or validate database connectivity. After reviewing, pass the command to migratorxpress_execute_command.

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'] for full migration, or ['diff'] for validation). Call migratorxpress_suggest_workflow to get the recommended task sequence.
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_modeNoHow to handle existing target database objects. preserve: keep existing objects. truncate: empty tables before loading. drop: drop and recreate objects.
compute_nbrowsNoCompute row counts for source tables before transfer
drop_tables_if_existsNoDrop target tables before creating them
load_modeNoHow to load data into target tables. truncate: clear target before loading. append: add to existing data.
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_modeNoHow to handle foreign key constraints. trusted: create as trusted. untrusted: create and verify. disabled: skip FK creation.
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
Behavior4/5

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

Annotations already indicate readOnlyHint and destructiveHint, and the description adds value by disclosing that passwords are masked and the command is not executed. While it does not describe the output format or error handling, it provides sufficient behavioral context beyond the annotations.

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 only three sentences, each serving a distinct purpose: stating the action, detailing a key feature (password masking), and providing the next step. It is highly concise and well-structured, with 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?

Despite the tool having 41 parameters and no output schema, the description is minimal and does not explain the return format, error handling, or how to interpret the preview. For such a complex tool, more context would be beneficial to ensure complete understanding, although the annotations and schema provide some support.

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 the parameters are fully documented in the schema. The description does not add any additional meaning or explanation beyond what the schema already provides, meeting the baseline but not exceeding it.

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 clearly states the tool builds and previews a migration command without executing it, specifying that it shows the exact CLI command with passwords masked. This distinguishes it from sibling migratorxpress_execute_command, providing a specific verb+resource with clear scope.

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 provides clear guidance by stating the command should be passed to migratorxpress_execute_command after review and explicitly notes it does not execute or validate connectivity. However, it does not explicitly state when not to use it or mention alternatives like migratorxpress_validate_auth_file, missing some exclusions.

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/arpeio-mcp'

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