coremcp
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": true
} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_table | Shows detailed schema information for a specific table including columns, types, keys, and relationships |
| execute_procedure | Executes a stored procedure by name with optional parameters. Parameters are passed as a JSON object string. Only available on non-read-only sources. |
| get_daily_salesB | Retrieves daily sales summary for a specific date |
| get_pending_orders | Gets all orders with pending status |
| get_top_customers | Lists top N customers by order count |
| list_proceduresA | Lists all stored procedures in a database source with their parameters. Use 'execute_procedure' to run one. |
| list_tables | Lists all available tables in a database source with their column counts |
| list_views | Lists all database views in a source with their columns. Views are virtual tables based on stored queries. |
| query_database | Executes a SQL query on a specified database source. Use this to retrieve data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| database_schema | Shows the complete database schema with tables, columns, types, and relationships |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely different purposes—one retrieves daily sales data, the other lists database procedures—so there is no ambiguity or overlap between them.
Both tools follow a consistent verb_noun pattern (get_daily_sales, list_procedures), making the naming predictable and easy to understand.
With only two tools, the server feels too sparse for the broad-sounding name 'coremcp'. The tools cover unrelated domains, suggesting the surface is underdeveloped.
The tool set is severely incomplete: there is no way to execute procedures (despite list_procedures suggesting it), no CRUD operations on sales data, and no clear domain cohesion. Agents will find the surface insufficient for practical use.