DatI
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_metadataA | Search tables, column definitions, and business semantic terms across databases connected to DatI. Behavior: - Read-only: Safe to call anytime with no side effects or destructive actions. Usage Guidelines: - Call this tool FIRST to discover existing tables, columns, and business terms before invoking execute_parameterized_sql. - Suitable for resolving NL2SQL schema ambiguity and understanding domain-specific abbreviations. |
| execute_parameterized_sqlA | Execute a pre-configured parameterized SQL tool published on the DatI MCP gateway. Behavior: - May mutate data depending on the configured SQL template (INSERT/UPDATE/DELETE). - Safe execution: Protected by DatI row-level permission guards and SQL parameter binding. Usage Guidelines: - Use this tool when you need to run specific business database operations. - Prerequisite: Use search_metadata first if you are unsure of the service or parameters. |
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 clearly distinct purposes: search_metadata is read-only discovery of schemas and terms, while execute_parameterized_sql runs a pre-configured SQL operation. There is no meaningful overlap or risk of misselection.
Both names use consistent snake_case with a verb-first pattern: search_metadata and execute_parameterized_sql. The convention is predictable and readable.
Only two tools are provided, which feels thin even for a focused MCP gateway. A minimal search-and-execute pair can work, but the surface is borderline and lacks supporting operations.
Metadata search and parameterized execution cover the core loop, but there is no explicit tool to discover the available parameterized SQL services or their parameters. This notable gap may force agents to rely on implicit knowledge.