Skip to main content
Glama
arpe-io

arpeio-mcp

Official
by arpe-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

fastbcp_info

Read-onlyIdempotent

Retrieve parallelism recommendations, export workflows, capabilities, or version info to plan database exports without connecting to a database.

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.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"
+]
  2. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful trait beyond that: it requires no database connectivity, which tells the agent this is a cheap local lookup. Return-content details are still absent.

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?

Three short sentences, front-loaded with the capability statement, then the action mechanism, then the operational caveat. Every sentence earns its place with no filler.

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 7-parameter, action-routed info tool with no output schema, the description and rich schema together give the agent enough to invoke it correctly. The only gap is that the description does not summarize the shape of what each action returns, which the missing output schema would otherwise have covered.

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 the enum for `action` already spells out which parameters each action requires, so the schema does the heavy lifting. The description adds nothing about parameter formats or conditional requirements beyond what the schema states.

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?

The description names a specific verb (Get information) and resource (FastBCP capabilities/parallelism/workflow/version), and the FastBCP product name implicitly separates it from fasttransfer_info, lakexpress_info, and migratorxpress_info. It never explicitly states the sibling distinction, so it falls short of a 5.

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?

It tells the agent to use the `action` parameter to select the information needed, which is implied routing rather than explicit when-to-use guidance. There is no statement of when to call this versus the preview/execute siblings, only that it is read-only and needs no database connectivity.

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