mcp-server-patterns
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Sets the stderr log level. | |
| MCP_MAX_OUTPUT_CHARS | No | Sets the response cap. Default 8000. | 8000 |
| WORKSPACE_<NAME>_TOKEN | No | Token for the workspace named <NAME>, upper-cased with non-alphanumerics replaced by underscores. Required for each workspace when using --config with real workspaces. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cancel_jobA | Cancel a queued or running job. Requires confirm=true; use dry_run=true to preview. |
| describe_tableB | Return the schema and row count of one table. |
| drop_tableA | Permanently drop a table. Requires confirm=true; use dry_run=true to preview. |
| get_jobB | Get one job run by id. |
| invoke_modelC | Run inference against a served model. |
| list_clustersB | List compute clusters and their state. |
| list_jobsB | List pipeline job runs, optionally filtered by status. Paginated. |
| list_modelsC | List served models and their state. |
| list_tablesB | List tables in the catalog, optionally filtered by name. Paginated. |
| list_workspacesA | List configured workspaces and whether a token is set (never the token itself). |
| run_jobC | Queue a new run of a pipeline. Not destructive, but it does change state. |
| sample_tableB | Return a small synthetic sample of rows from a table. |
| start_clusterC | Start a cluster. Safe to repeat. |
| terminate_clusterA | Terminate a running cluster. Requires confirm=true; use dry_run=true to preview. |
| vector_searchC | Semantic search over a vector index. Returns the top_k closest documents. |
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 15 tools
Each tool targets a clearly distinct resource/action: table inspection, job lifecycle, cluster lifecycle, model listing/invocation, workspace listing, and vector search. Tools like list_tables, describe_table, and sample_table are related but have unambiguous distinctions, and no two tools appear to do the same thing.
Nearly all tools follow a consistent snake_case verb_noun pattern, and singular/plural resource naming is used conventionally. The only mild deviation is vector_search, which follows a noun_verb form but remains clear and readable.
The server exposes 15 tools, which is at the upper end of the ideal range but still well-scoped for a data-platform control surface. Each tool maps to a meaningful operation across tables, jobs, clusters, models, workspaces, or search.
Core operational coverage is present for listing, inspecting, running/canceling jobs, starting/terminating clusters, and invoking models. However, there are notable gaps such as creating/altering tables, detailed get operations for clusters/models/workspaces, and model deployment/update workflows.