Boxtalk Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_CONFIG_PATH | No | The path to the SQL Server configuration JSON file containing database credentials and options. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_table_dataC | Get paginated data from a SQL Server table. Returns a specified page of records with pagination enforced. |
| get_table_countB | Get the total count of records in a SQL Server table. |
| get_table_structureA | Get the structure/schema of a SQL Server table including column names, data types, and constraints. |
| query_dataA | Execute a SELECT query on the SQL Server database with enforced pagination. Only SELECT queries are allowed - DDL and DML operations (CREATE, ALTER, DROP, INSERT, UPDATE, DELETE, etc.) are rejected. |
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
Each tool has a clearly distinct purpose with no overlap: get_table_count retrieves record counts, get_table_data fetches paginated data, get_table_structure provides schema details, and query_data executes custom SELECT queries. The descriptions clearly differentiate between metadata operations and data retrieval, eliminating any potential for misselection.
All tool names follow a consistent verb_noun pattern using snake_case: get_table_count, get_table_data, get_table_structure, and query_data. The naming convention is perfectly uniform throughout the set, making the tools predictable and easy to understand at a glance.
Four tools is an ideal number for this SQL Server data access server, providing a well-scoped surface that covers essential operations without being overwhelming. Each tool serves a distinct and necessary function for interacting with database tables, making the count perfectly appropriate for the domain.
The tool set provides strong coverage for read-only data access with pagination, schema inspection, and custom queries, but lacks write operations (INSERT, UPDATE, DELETE) which might be expected in a full database interaction suite. However, given the enforced SELECT-only limitation in query_data, this appears intentional rather than a gap, though it limits the server's scope.