SP Database MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_table_infoA | 获取指定数据库表的结构信息，包括字段定义、类型、注释等。支持两种查询方式：1) 低代码系统schema查询（通过da_logic_entity和da_entity_attribute表）；2) 传统数据库元数据查询。优先使用低代码系统方式获取更详细的字段信息。 |
| search_tablesC | 根据关键词搜索数据库表 |
| list_all_tablesC | 列出所有数据库表 |
| get_table_documentationC | 获取表的详细文档说明 |
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 4 tools
The tools are mostly distinct with clear purposes: list_all_tables enumerates all tables, search_tables finds tables by keyword, get_table_info retrieves structural details, and get_table_documentation provides documentation. However, get_table_info and get_table_documentation could be slightly ambiguous as both relate to table details, but their descriptions differentiate them well (structure vs. documentation).
All tool names follow a consistent verb_noun pattern using snake_case: get_table_documentation, get_table_info, list_all_tables, and search_tables. The naming is predictable and readable throughout the set.
With 4 tools, the count is well-scoped for a database documentation server. Each tool serves a distinct function in exploring and understanding database tables, and there are no unnecessary or redundant tools.
The toolset covers core exploration needs: listing, searching, and retrieving table information and documentation. Minor gaps exist, such as no tools for updating or managing tables (e.g., create or modify operations), but this is reasonable for a read-only documentation server focused on querying metadata.