mcp-chinookdb-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
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 |
|---|---|
| run_sql_queryA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_all_tables | Generate a prompt to list all tables in the database using the schema resource. Returns a list of MCP prompt messages for LLMs. |
| show_table_schema | Generate a prompt to show the schema for a specific table. Args: table_name: The name of the table to show the schema for. Returns: A string prompt for the LLM. |
| count_table_rows | Generate a prompt to count the number of rows in a specific table. Args: table_name: The name of the table to count rows from. Returns: A string prompt for the LLM. |
| query_top_artists | Generate a prompt to find the top N artists by the number of tracks they have. Args: limit: The number of top artists to retrieve (default is 5). Returns: A string prompt for the LLM. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_tables_schema | Provides the schema for all tables in the Chinook database. Returns a formatted string with the schema of each table. |
TDQS
Scored across 1 tool
Only one tool exists, so no ambiguity whatsoever.
Single tool uses clear snake_case verb_noun pattern, perfectly consistent.
One tool is on the low end; while it covers the core querying need, a few additional tools for schema discovery would improve utility.
Provides the essential SELECT query capability but lacks metadata tools (e.g., list tables, describe columns), which agents may need to form correct queries.