Skip to main content
Glama
Sign In
arpeio-mcp

arpeio-mcp

Official
by arpe-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arpe_quick_start

Read-onlyIdempotent

Recommends the right Arpe.io tool and step-by-step workflow from a plain-English use case when intent is unclear, including parameters and call sequence; does not execute commands.

Instructions

Determine which Arpe.io tool to use and get a step-by-step workflow guide. Call this when the user's intent is unclear or they are new to arpe.io tools. Accepts a plain English use case description and returns the recommended tool, required parameters, and the sequence of tool calls to make. Does not execute anything.

Input Schema

NameRequiredDescriptionDefault
productNoOverride auto-detection and show the workflow for a specific product ('adbc' for the Arpe ADBC drivers). If omitted, the tool selects based on use_case.
use_caseYesPlain English description of what the user wants to do (e.g., 'export a large Oracle table to S3 as Parquet', 'migrate SQL Server schema to PostgreSQL'). Used to auto-detect the right tool.

Output Schema

NameRequiredDescriptionDefault
stepsNoRecommended sequence of tool calls.
statusYes'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.
warningNoCross-tool caveat (e.g. internal use of FastBCP/FastTransfer).
selected_productNoRecommended product, 'all', or null if undetermined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.9
    • changedInput schema / properties / product / description
      Previous value: -"Override auto-detection and show the workflow for a specific product. If omitted, the tool selects based on use_case."New value: +"Override auto-detection and show the workflow for a specific product ('adbc' for the Arpe ADBC drivers). If omitted, the tool selects based on use_case."
    • changedInput schema / properties / product / enum
      Previous value: -[
-  "fastbcp",
-  "fasttransfer",
-  "lakexpress",
-  "migratorxpress",
-  "all"
-]New value: +[
+  "fastbcp",
+  "fasttransfer",
+  "lakexpress",
+  "migratorxpress",
+  "adbc",
+  "all"
+]
  2. Changed1 schema field changedv0.3.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "selected_product": {
+      "description": "Recommended product, 'all', or null if undetermined.",
+      "type": "string"
+    },
+    "status": {
+      "description": "'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.",
+      "enum": [
+        "ok",
+        "error"
+      ],
+      "type": "string"
+    },
+    "steps": {
+      "description": "Recommended sequence of tool calls.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "warning": {
+      "description": "Cross-tool caveat (e.g. internal use of FastBCP/FastTransfer).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  3. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond that: it explains what the call produces (recommended tool, required parameters, sequence of calls) and reinforces that nothing is executed. It does not discuss latency or how 'all' vs a specific product changes the output volume, which keeps it below 5.

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?

Four short sentences, front-loaded with the purpose and then the trigger condition, with no filler. Slight redundancy in restating non-execution after the 'workflow guide' framing, but it earns its place as a safety signal.

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 routing tool with an output schema and fully documented params, the description covers what it does, when to use it, and what it returns. The only gap is guidance on how results differ when the user already knows the product, which the enum hints at but the prose never addresses.

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 coverage is 100%, including an enum on 'product' with a clear description, so the schema carries the parameter burden. The description only paraphrases the use_case parameter ('Accepts a plain English use case description') and never mentions the 'product' override, adding essentially no meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Determine which Arpe.io tool to use and get a step-by-step workflow guide') and explicitly separates itself from the execute_* siblings with 'Does not execute anything.' An agent can immediately tell this is a router/advisory tool rather than an action tool.

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?

Gives a clear trigger condition: 'Call this when the user's intent is unclear or they are new to arpe.io tools.' It does not name concrete alternatives for the clear-intent case (e.g. 'go straight to fastbcp_execute_export'), but the readOnly/non-executing framing makes the boundary with action siblings fairly obvious.

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