tablebridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TABLEBRIDGE_DATA_DIR | No | Directory of files to expose (the sandbox boundary) | . |
| TABLEBRIDGE_MAX_ROWS | No | Max rows returned per query/preview | 1000 |
| TABLEBRIDGE_RECURSIVE | No | Scan subdirectories too | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | List the tables available to query (one per data file) with column counts. Start here: each CSV/Parquet/JSON file under the data directory is exposed as a table you can SELECT from and JOIN across. |
| describeC | Show a table's columns and types. |
| previewA | Return the first |
| queryA | Run a read-only SQL query (DuckDB dialect) across the loaded tables. Supports SELECT / WITH / DESCRIBE / SUMMARIZE and JOINs across files. Writes
and raw file-access functions are rejected. Results are capped at
TABLEBRIDGE_MAX_ROWS; a |
| refreshA | Re-scan the data directory (pick up added/changed files) and report the count. |
| server_infoA | Report the effective configuration (data dir, row cap, supported formats). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: describe for schema, list_sources for table listing, preview for row sampling, query for SQL execution, refresh for data reload, and server_info for configuration. No overlap.
Most tools use single imperative verbs (describe, preview, query, refresh) but list_sources uses verb_noun and server_info uses noun_noun. The pattern is mostly consistent but has minor deviations.
With 6 tools, the server covers all core functionalities needed for data exploration and querying without excess or deficiency. The scope is well-matched.
The tool set provides essential operations: listing, describing, previewing, querying, refreshing, and configuration. A minor gap could be the absence of a statistical summary tool, but the core workflow is fully covered.