labs-catalog-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_labsA | List the portfolio's labs, optionally filtered by collection (0-5) or live mode (LIVE/SIMULATED). |
| get_labB | Full detail for one lab: the problem it addresses, the decision it enables, status, and route. |
| search_decisionsA | Search the catalog by the enterprise decision you are facing (matches problem/decision/title text). |
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 targets a distinct operation: retrieving full details of a single lab, listing labs with filters, and searching by decision text. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (get_lab, list_labs, search_decisions), making the set predictable and easy to navigate.
Three tools is an appropriate size for a focused catalog service, covering the primary use cases of detail retrieval, listing, and search without unnecessary bloat.
The tools provide full coverage for a read-only catalog: listing with filters, full detail retrieval, and full-text search. No obvious gaps exist for the stated purpose.