AI Workbench 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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_promptsA | List the bundled prompt templates and assistant blueprints available in this local catalog. |
| render_promptA | Render one bundled prompt template using supplied string variables. Returns text only and does not call an AI provider. |
| get_assistantA | Return one bundled assistant blueprint formatted for a selected host. This does not create, install, publish, or modify an assistant account. |
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 action and resource: list_prompts enumerates the catalog, render_prompt renders a specific template, and get_assistant retrieves a blueprint. The list vs get distinction is clear, with no overlapping purposes.
All names follow a consistent verb_noun snake_case pattern: list_prompts, render_prompt, get_assistant. Pluralization varies logically (list many vs render/get one), but the convention is uniform.
Three tools are well-suited to a read-only local catalog, covering the essential operations of enumerating, rendering, and retrieving. The count is minimal but each tool earns its place, with no bloat or missing core function.
The surface covers listing, rendering, and retrieving, but lacks a direct way to get a raw prompt template without rendering it (e.g., get_prompt) or a generic assistant blueprint without host selection. These are minor gaps for a small catalog that agents can likely work around.