mcp-data-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DATA_AGENT_DB | No | Path to a different database file to point the tools at. The default uses the bundled SQLite dataset. | |
| MCP_DATA_AGENT_LLM_MODEL | No | Model name for the optional real LLM provider. Must be set together with MCP_DATA_AGENT_LLM_ENDPOINT and MCP_DATA_AGENT_LLM_API_KEY. | |
| MCP_DATA_AGENT_LLM_API_KEY | No | API key for the optional real LLM provider. Must be set together with MCP_DATA_AGENT_LLM_ENDPOINT and MCP_DATA_AGENT_LLM_MODEL. | |
| MCP_DATA_AGENT_LLM_ENDPOINT | No | Generic chat-completions style endpoint for an optional real LLM provider. Must be set together with MCP_DATA_AGENT_LLM_MODEL and MCP_DATA_AGENT_LLM_API_KEY; otherwise the deterministic MockLLM planner is used. |
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 |
|---|---|
| list_tablesA | List every table in the database with its row count. |
| describe_tableA | Describe one table: column names, types, nullability, primary key. |
| run_queryA | Run a single read-only SELECT query. Writes, DDL, multiple statements and SQL comments are rejected. Results are capped at 100 rows and queries time out after 5 seconds. |
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 3 tools
The three tools target clearly distinct operations: listing tables, describing a single table's schema, and executing a SELECT query. There is no overlap between schema discovery and query execution, so an agent can easily select the right tool.
All tools follow a consistent snake_case verb_noun pattern: list_tables, describe_table, run_query. The convention is predictable and readable throughout.
Three tools is a tight, well-scoped surface for a read-only data agent: each tool earns its place and covers a necessary stage of exploration. There are no redundant or filler tools.
The surface covers the core read-only workflow: discover tables, inspect schema, then query data. Minor gaps like schema/table search or query plan explanation exist, but agents can work around them with the provided tools.