QueryBridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | No | MySQL server host | 127.0.0.1 |
| DB_NAME | No | Database name | mcp_db |
| DB_PORT | No | Database port | 3306 |
| DB_USER | No | Database username | root |
| LLM_MODEL | No | Ollama model used for text generation | llama3.1 |
| TABLE_NAME | No | Name of the database table to query | employee_salary |
| DB_PASSWORD | No | Database password | root |
| EMBEDDING_MODEL | No | Ollama embedding model used for vector operations | nomic-embed-text |
| OLLAMA_BASE_URL | No | Ollama API base URL | http://localhost:11434 |
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 |
|---|---|
| get_employee_salary_schemaA | Return the schema of the employee_salary table for AI/agent use. |
| read_employee_salaryA | Read the latest rows from employee_salary. Keep the result small for LLM use. |
| query_employee_salaryA | Run a read-only SQL query against the employee_salary table. Only SELECT statements are allowed. |
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
Each tool has a clearly distinct purpose: schema introspection, small sample reads, and arbitrary read-only SQL queries. The read and query tools could theoretically overlap, but their descriptions make the intended use obvious.
All tool names follow a consistent verb_noun pattern around the employee_salary entity. get, read, and query are different verbs but align naturally with each tool's specific action.
Three tools is well-scoped for a focused server that exposes one table with schema, sample data, and ad-hoc querying. There are no unnecessary extras and nothing feels missing.
The server fully covers its intended read-only domain: understanding the schema, seeing recent rows, and running arbitrary SELECT queries. Write operations are not needed given the explicit read-only scope.