Boxtalk Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_CONFIG_PATH | No | Path to the custom configuration file (JSON) containing SQL Server database credentials and connection options. If not provided, the server typically looks for config.json in the application directory. |
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: get_table_count retrieves record counts, get_table_data fetches paginated records, get_table_structure provides schema information, and query_data executes custom SELECT queries. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_table_count, get_table_data, get_table_structure, query_data). The naming is uniform and predictable, with 'get_' prefix for three tools and 'query_' for the fourth, both clearly indicating actions on data resources.
With 4 tools, this server is well-scoped for its purpose of SQL Server data access. Each tool earns its place by covering essential operations: counting, retrieving, inspecting structure, and querying data. The count is neither too sparse nor bloated, fitting the domain appropriately.
The toolset provides strong coverage for read-only data access, including counts, paginated data, schema, and custom queries. However, there are minor gaps, such as no tools for metadata operations (e.g., listing tables or databases) or handling non-SELECT queries, which agents might need to work around for broader database interactions.