Skip to main content
Glama
arpeio-mcp

arpeio-mcp

Official
by arpe-io

adbc_info

Read-onlyIdempotent

List Arpe ADBC drivers and versions, or retrieve one driver's load name, connection URI, authentication, install command and docs links; no database connection needed.

Instructions

Get information about the Arpe ADBC drivers: ArpeMSSQL (SQL Server), ArpePGSQL (PostgreSQL), ArpeOracle (Oracle), ArpeNetezza (Netezza), ArpeTeradata (Teradata) and ArpeDb2 (IBM Db2). They are native, licence-gated ADBC drivers that return Apache Arrow from any ADBC client (Python, C/C++, C#, Go, Java, R, Rust) and back FastBCP's adbc_* connection types. Omit driver to list the family with current versions; pass it for the load name, connection URI, authentication, install command and docs links of one driver. Read-only, does not require database connectivity.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adbc_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
driverNoOptional driver: ArpeMSSQL (arpemssql), ArpePGSQL (arpepgsql), ArpeOracle (arpeoracle), ArpeNetezza (arpenz), ArpeTeradata (arpeteradata), ArpeDb2 (arpedb2). The commercial name, the load name or the FastBCP connection type (e.g. 'adbc_teradata') are all accepted.

Output Schema

NameRequiredDescriptionDefault
statusYes'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.
driversNoDriver records (all drivers, or the requested one).
installNoOne-line installers (single driver only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.13
    • changedInput schema / properties / driver / description
      Previous value: -"Optional driver: ArpeMSSQL (arpemssql), ArpePGSQL (arpepgsql), ArpeOracle (arpeoracle), ArpeNetezza (arpenz), ArpeTeradata (arpeteradata). The commercial name, the load name or the FastBCP connection type (e.g. 'adbc_teradata') are all accepted."New value: +"Optional driver: ArpeMSSQL (arpemssql), ArpePGSQL (arpepgsql), ArpeOracle (arpeoracle), ArpeNetezza (arpenz), ArpeTeradata (arpeteradata), ArpeDb2 (arpedb2). The commercial name, the load name or the FastBCP connection type (e.g. 'adbc_teradata') are all accepted."
  2. Addedv0.3.9

TDQS

A3.6/5.0
Behavior3/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 real context beyond them ('does not require database connectivity') and previews what each mode returns, but 'Read-only' largely restates the annotations rather than extending them.

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

Conciseness3/5

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

The mode-selection guidance is front-loaded and the structure is sound, but the driver enumeration and the client-language list ('Python, C/C++, C#, Go, Java, R, Rust') read as marketing padding that does not help an agent decide or invoke. Trimming those would sharpen it without losing any invocation-relevant information.

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?

With an output schema present and a single optional parameter, the description covers what an agent needs: both modes, the accepted identifier forms, and the fact that no live database connection is required. Only the absence of any routing to sibling info tools keeps it from full marks.

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 single `driver` parameter's accepted aliases (commercial name, load name, connection type like 'adbc_teradata') are already documented in the schema. The description's added value is the behavioral distinction between omitting the param (family listing with versions) and supplying it (single-driver detail), which is useful but marginal.

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 and resource ('Get information about the Arpe ADBC drivers') and enumerates the six concrete drivers, so an agent knows exactly what domain it covers. It does not explicitly contrast itself with siblings such as fastbcp_info or search_docs, which keeps it 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 Guidelines4/5

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

It gives concrete mode selection: omit `driver` to list the family with versions, pass it to get load name, URI, auth, install command and docs for one driver. That is explicit when-to-use guidance, but there is no statement of when NOT to use this tool or which sibling to pick for other Arpe/FastBCP information.

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