Skip to main content
Glama
arpe-io

arpeio-mcp

Official
by arpe-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

fastbcp_info

Read-onlyIdempotent

Get FastBCP capabilities, recommended parallelism, workflow steps, or binary version for database exports across supported formats and storage targets; read-only, no database connection.

Instructions

Get information about FastBCP capabilities, parallelism recommendations, workflow guidance, or binary version. Use action to select what information you need. Read-only, does not require database connectivity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat information to retrieve. formats: list supported source databases, output formats, and storage targets. parallelism: get a recommended parallelism method for a specific table (requires source_type, has_numeric_key, table_size_estimate). workflow: get a step-by-step export guide with database-specific tips (requires source_type, output_format). version: report installed binary version and capabilities.
source_typeNoSource database type (required for action=parallelism and action=workflow)
output_formatNoDesired output format (required for action=workflow)
storage_targetNoStorage target (optional, for action=workflow, default: local)local
has_numeric_keyNoWhether the table has a numeric key column (required for action=parallelism)
has_identity_columnNoWhether the table has an identity/auto-increment column (optional, for action=parallelism)
table_size_estimateNoEstimated table size (required for action=parallelism). small: <100K rows. medium: 100K-10M. large: >10M.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.6
    • changedInput schema / properties / source_type / enum
      Previous value: -[
-  "clickhouse",
-  "hana",
-  "mssql",
-  "msoledbsql",
-  "mysql",
-  "nzcopy",
-  "nzoledb",
-  "nzsql",
-  "odbc",
-  "oledb",
-  "oraodp",
-  "pgcopy",
-  "pgsql",
-  "teradata",
-  "adbc_mssql",
-  "adbc_pgsql",
-  "adbc_oracle"
-]New value: +[
+  "clickhouse",
+  "hana",
+  "mssql",
+  "msoledbsql",
+  "mysql",
+  "nzcopy",
+  "nzoledb",
+  "nzsql",
+  "odbc",
+  "oledb",
+  "oraodp",
+  "pgcopy",
+  "pgsql",
+  "teradata",
+  "adbc_mssql",
+  "adbc_pgsql",
+  "adbc_oracle",
+  "adbc_netezza"
+]
  2. Changed1 schema field changedv0.3.5
    • changedInput schema / properties / source_type / enum
      Previous value: -[
-  "clickhouse",
-  "hana",
-  "mssql",
-  "msoledbsql",
-  "mysql",
-  "nzcopy",
-  "nzoledb",
-  "nzsql",
-  "odbc",
-  "oledb",
-  "oraodp",
-  "pgcopy",
-  "pgsql",
-  "teradata"
-]New value: +[
+  "clickhouse",
+  "hana",
+  "mssql",
+  "msoledbsql",
+  "mysql",
+  "nzcopy",
+  "nzoledb",
+  "nzsql",
+  "odbc",
+  "oledb",
+  "oraodp",
+  "pgcopy",
+  "pgsql",
+  "teradata",
+  "adbc_mssql",
+  "adbc_pgsql",
+  "adbc_oracle"
+]
  3. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: it requires no database connectivity, lowering the cost/risk of calling it as a discovery step. It does not describe output shape, but the annotation bar is already met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with what is retrieved, followed by the read-only/no-connectivity note. The 'Use `action` to select' clause is mildly redundant with the schema, but overall there is little waste.

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?

For a read-only info tool with full schema coverage and complete annotations, the description is nearly sufficient. It could be more complete by noting that action-specific required params must be supplied together, but nothing critical for correct invocation is missing, and no output schema means return values need no explanation.

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% and each parameter documents its per-action requirement (e.g. source_type required for parallelism/workflow), so the schema does the heavy lifting. The description only restates that `action` selects the information, adding no syntax or dependency detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: get FastBCP capability/workflow/parallelism/version info, with the action enum naming the four information categories. It is clear what the tool does, but it never distinguishes itself from sibling info tools like fasttransfer_info, lakexpress_info, or migratorxpress_info that occupy the same 'get info' niche.

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

Usage Guidelines3/5

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

Tells the agent to use `action` to select the needed information and notes it is read-only with no DB connectivity, implying a safe discovery call. However, it gives no when-to-use guidance versus the many sibling *_info and *_preview tools, nor any hint about sequencing with fastbcp_execute_export.

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

Deploy Server

Other Tools