Skip to main content
Glama
arpe-io

arpeio-mcp

Official
by arpe-io

lakexpress_preview_command

Read-onlyIdempotent

Build and preview a LakeXpress CLI command without executing it. Shows the exact command to run, enabling review before execution.

Instructions

Build and preview a LakeXpress CLI command WITHOUT executing it. Call this after lakexpress_info with action='workflow' to build each command in the recommended sequence. Shows the exact command that will be run. Does NOT execute the command or validate connections. After reviewing, pass the command to lakexpress_execute_command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runNoRun a multi-step pipeline from a YAML config file.
syncNoRun a full sync (export + publish). Exports data and publishes if configured.
statusNoShow sync run status and history.
cleanupNoClean up old or failed sync runs.
commandYesThe LakeXpress command to run. logdb_init/lxdb_init: initialize databases. config_create: set up sync configuration. sync/sync_export/sync_publish: execute pipeline steps. run: full pipeline execution. status: check pipeline status. cleanup: remove completed data.
os_typeNoTarget operating system for command formattinglinux
lxdb_dropNoDrop the log database schema (0.3.0+ replacement for logdb_drop). WARNING: permanently deletes all sync history.
lxdb_initNoInitialize the log database schema (0.3.0+ replacement for logdb_init).
logdb_dropNoDrop the log database schema. WARNING: permanently deletes all sync history and configuration.
logdb_initNoInitialize the log database schema. Creates required tables for sync management.
lxdb_locksNoShow currently locked tables in the log database (0.3.0+ replacement for logdb_locks).
config_listNoList all sync configurations.
logdb_locksNoShow currently locked tables in the log database.
sync_exportNoRun export-only sync (no publish). Exports data to local or cloud storage.
sync_publishNoRun publish-only sync. Publishes previously exported data to the configured target.
config_createNoCreate a new sync configuration. Requires source DB credentials and either output_dir (local) or target_storage_id (cloud). Add publish_target for data lake publishing.
config_deleteNoDelete a sync configuration.
lxdb_truncateNoClear all data from the log database while keeping the schema (0.3.0+ replacement for logdb_truncate).
logdb_truncateNoClear all data from the log database while keeping the schema.
lxdb_release_locksNoRelease stale or stuck table locks (0.3.0+ replacement for logdb_release_locks).
logdb_release_locksNoRelease stale or stuck table locks in the log database.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipsNoSuggested next tool calls to resolve errors.
errorsNoField-level validation errors (status='error').
statusYes'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.
commandNoFull CLI argv, ready to hand to the execute tool.
warningsNoVersion-compatibility warnings.
explanationNoHuman-readable summary of what the command does.
command_typeNoWhich LakeXpress sub-command was built.
preview_onlyNoTrue when no binary is configured (execution unavailable).
command_stringNoThe argv joined into one command string.
command_displayNoThe command formatted for display, safe to show the user.
Behavior5/5

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

The description confirms the no-side-effect nature (read-only, idempotent) matching annotations. It adds transparency by noting it does not execute or validate connections, beyond what annotations declare.

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 concise (4 sentences) and front-loaded with the main purpose. Every sentence is informative and earns its place.

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?

Given the complexity (21 parameters, nested objects, many sub-commands), the description provides clear usage flow. The output schema exists, so return values are documented elsewhere. Minor gap: no explicit mention of output format beyond 'shows the exact command', but the schema covers it.

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 baseline is 3. The description does not add parameter-level explanations, but the schema already provides thorough descriptions for all properties.

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 LakeXpress CLI command without executing it. It explicitly distinguishes itself from the sibling tool lakexpress_execute_command and provides a specific use case: call after lakexpress_info with action='workflow'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: after lakexpress_info, before lakexpress_execute_command. It also states what it does not do (execute, validate connections), helping the agent decide when to use this preview tool versus 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/arpeio-mcp'

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