Rowbase
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| guideA | Read this first, once per session: the Rowbase knowledge base — recommended workflow, safety rules (read-only model, one statement per call), the TOON output format and SQL dialect notes. Use it before any other tool; it needs no connection. Returns a markdown document. |
| connectionsA | List the user's saved database connections exposed to MCP. Call this first to get the exact connection names every other tool requires. Returns a table connections[N]{name,driver,env,mode,database,tunnel} — mode is the EFFECTIVE read-only/read-write mode for MCP; env 'prod' means be extra careful — plus writes_enabled_in_mcp. No pagination: all exposed connections are returned. |
| databasesA | List the databases on a connection's server and which one is current. Use it when a connection has no database selected, or to work in another database (pass |
| tablesA | List all tables and views of a connection/database with approximate row counts — the entry point for browsing. Use |
| describeA | Show the structure of one known table: columns with type, nullability, key, default, foreign-key target (fk = table.column — use it to write JOINs) and comment, plus indexes and the tables that reference it. Use it before writing SQL against a table; use |
| search_schemaA | Find tables and columns whose name contains a keyword (case-insensitive substring; on MySQL also column comments). Use it when you know WHAT you are looking for but not WHERE it is stored; use |
| sampleA | Peek at a few real rows of one table (SELECT * … LIMIT n, in storage order, no sorting) to see what the data looks like before writing a query. Use |
| countA | Return the exact number of rows in a table, optionally filtered — use it to size a result before fetching it or to answer 'how many' questions. Use |
| queryA | Run exactly ONE SQL statement — the general tool for answering questions: specific columns, JOINs (follow fk from |
| explainA | Show how the database will execute a SELECT (its query plan) to diagnose slow queries or check index use — use it instead of |
| find_refA | Find which table holds a UUID value as its primary key — for schemas that store references as UUIDs without foreign keys (1C-style |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup | Set up this assistant to work with Rowbase: read the guide, list connections and create a reusable skill. |
| explore | Explore a connection and summarize its data model. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Rowbase guide | Knowledge base: workflow, safety, output format, tools. |
| Connections |
TDQS
Scored across 11 tools
Each tool targets a distinct step or resource in the database exploration workflow: guide, connections, databases, tables, search_schema, describe, find_ref, sample, count, query, and explain. Descriptions explicitly cross-reference alternatives (e.g., use search_schema when you don't know the table, use query instead of sample for joins), leaving no meaningful overlap.
All names are lowercase snake_case with no casing or separator inconsistencies. However, the set mixes noun-style list tools (connections, databases, tables) with verb-style action tools (describe, sample, query), so it is not a strict verb_noun pattern throughout.
Eleven tools is well within the ideal range and each tool earns its place: discovery, schema inspection, sampling, counting, querying, performance analysis, and reference resolution. No tool feels redundant or excessive for a read-only database assistant.
The surface covers the full read-only lifecycle from connection discovery through schema browsing, targeted search, structure inspection, sampling, exact counts, general SQL, query plans, and UUID reference resolution. There are no obvious dead ends for the stated purpose, and write operations are intentionally limited by the read-only model.