GABI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESS_TOKEN | Yes | The access token for the GABI endpoint | |
| GABI_ENDPOINT | Yes | The endpoint URL for GABI |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_db_nameC | Get the name of the current database. Args: |
| get_query_resultC | Executes an SQL query on a single line against the current database. Args: query |
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 2 tools
The two tools have completely distinct purposes: one retrieves the database name, while the other executes SQL queries. There is no overlap or ambiguity between them, making it clear which tool to use for each task.
Both tools follow a consistent verb_noun pattern with 'get_' prefixes (get_db_name and get_query_result). This naming convention is uniform and predictable across the tool set.
With only 2 tools, the server feels thin for a database interaction domain. It lacks essential operations like create, update, or delete queries, making it insufficient for typical database workflows. The count is too low for the apparent scope.
The tool set is severely incomplete for database operations. It only allows retrieving the database name and executing queries, missing critical CRUD operations (e.g., insert, update, delete) and other common functions like listing tables or managing connections. This will cause significant agent failures in handling database tasks.