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 before passing to execute.

Instructions

Build and preview a LakeXpress CLI command WITHOUT executing it. Call this after lakexpress_suggest_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
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.
logdb_initNoInitialize the log database schema. Creates required tables for sync management.
logdb_dropNoDrop the log database schema. WARNING: permanently deletes all sync history and configuration.
logdb_truncateNoClear all data from the log database while keeping the schema.
logdb_locksNoShow currently locked tables in the log database.
logdb_release_locksNoRelease stale or stuck table locks in the log database.
lxdb_initNoInitialize the log database schema (0.3.0+ replacement for logdb_init).
lxdb_dropNoDrop the log database schema (0.3.0+ replacement for logdb_drop). WARNING: permanently deletes all sync history.
lxdb_truncateNoClear all data from the log database while keeping the schema (0.3.0+ replacement for logdb_truncate).
lxdb_locksNoShow currently locked tables in the log database (0.3.0+ replacement for logdb_locks).
lxdb_release_locksNoRelease stale or stuck table locks (0.3.0+ replacement for logdb_release_locks).
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.
config_listNoList all sync configurations.
syncNoRun a full sync (export + publish). Exports data and publishes if configured.
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.
runNoRun a multi-step pipeline from a YAML config file.
statusNoShow sync run status and history.
cleanupNoClean up old or failed sync runs.
os_typeNoTarget operating system for command formattinglinux
Behavior5/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context beyond annotations: 'Does NOT execute the command or validate connections' and 'Shows the exact command that will be run.' This is excellent transparency.

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 extremely concise with three sentences. It is front-loaded: the first sentence immediately states the core purpose. Every sentence provides critical information without fluff.

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?

The description is adequate for a preview tool but assumes the user knows the workflow and the structure of the command parameter. It does not explain how to construct the command object or the significance of the various subcommands. Given the nested schema complexity, more context would help.

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 any additional meaning to the parameters beyond what the schema already provides. It neither explains the command enum nor the nested objects.

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 the tool builds and previews a LakeXpress CLI command without executing it. It includes the specific verb+resource ('Build and preview a LakeXpress CLI command') and distinguishes itself from sibling tools like lakexpress_execute_command by clarifying it does not execute.

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 when-to-use guidance: 'Call this after lakexpress_suggest_workflow to build each command in the recommended sequence.' It also directs the user to pass the command to lakexpress_execute_command afterward. It lacks explicit when-not-to-use scenarios but is still quite helpful.

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