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 |
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 10 tools
Each tool targets a distinct stage of database exploration or querying, and descriptions explicitly state when to use one over another (e.g., sample vs query, count vs query, explain vs query). The only overlap is that query can technically perform many tasks, but the guidance makes boundaries clear.
Names mix plural nouns (connections, databases, tables), verbs (describe, sample, count, query, explain), and one snake_case verb_noun (search_schema). While readable, there is no consistent pattern, so agents cannot rely on naming alone to infer tool type.
Ten tools is well-scoped for a database MCP, covering connection discovery, schema browsing, data sampling, counting, querying, and performance analysis. Each tool has a clear role, and no tool feels superfluous.
The surface covers the full read-only query lifecycle from connections and databases to tables, schema search, sampling, counting, querying, and explain plans. Writes are possible via query when enabled, and no major operations for the stated domain are missing.