Prebuilt and Custom Tools
The following table summarizes the Database Tools MCP toolset types, whether the tools are prebuilt or custom, the specific tool names, and the default allowed roles required to use them.
Table 5-1 Toolsets
| Toolset Type | Tool type | Tool Name | Description | Default Allowed Roles |
|---|---|---|---|---|
| Custom SQL | Custom | Customized tool name | Use this tool when you want to define one. | MCP_Operator |
| Built-in SQL | Prebuilt | dbtools_execute_sql |
Use this tool when you need to directly query or modify the database, inspect schema objects, or run procedural logic. The source argument should contain the SQL or script to execute. |
MCP_Operator |
| Customizable Reporting Tools | Prebuilt |
dbtools_list_reports |
Use this tool to discover which reports exist and to obtain their metadata, including the report ID (ID of the SQL report), display name, description, purpose, and usage instructions. The returned reportId values are required when calling dbtools_execute_report or dbtools_get_report_sql. | MCP_User, MCP_Operator, MCP_Administrator |
|
dbtools_execute_report |
Provide the reportId of the report to run, along with any required variable values. Variable placeholders defined by the report will be substituted with the supplied arguments at execution time. The result set is returned as CSV-formatted content, making it easy to consume programmatically or display to users. Use dbtools_list_reports to identify the correct reportId before calling this tool. |
MCP_User, MCP_Operator, MCP_Administrator | ||
| dbtools_get_report_sql |
Use this tool when you need to inspect, understand, or customize the SQL used by a report. The returned SQL can be modified and executed directly using dbtools_execute_sql. The tool expects a valid reportId, which can be obtained from dbtools_list_reports. |
MCP_Operator | ||
| dbtools_get_tool_request |
Retrieves the current status and (if available) the final result of a previously submitted asynchronous tool call. |
MCP_Operator |