gpt-subagents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key |
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 |
|---|---|
| ask_gptA | Ask an OpenAI model as an expert subagent. ONE tool for everything: you choose the |
| list_patternsA | List available orchestration patterns for driving ask_gpt. Call this before non-trivial expert work — reviews, audits, threat modeling, large-document analysis — then read the chosen one with get_pattern. Returns each pattern's name, title, summary, and when to use it. |
| get_patternA | Return the full text of an orchestration pattern by name (see list_patterns). Use it to apply the pattern when orchestrating ask_gpt calls. |
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 serves a clear, distinct purpose: ask_gpt for executing model calls, list_patterns for browsing patterns, and get_pattern for retrieving pattern details. No functional overlap exists.
All tool names follow a consistent verb_noun pattern (ask_gpt, list_patterns, get_pattern), making it predictable for an agent.
With 3 tools, the set is compact but well-scoped for its purpose: a single execution tool and two pattern retrieval utilities. Slightly on the small side, but not underdeveloped.
The core functionality and pattern management are covered. Minor gaps exist (e.g., no tool to view conversation history or manage context), but the overall surface is sufficient for the intended use.