Skip to main content
Glama
Wally-Ahmed

gpt-subagents-subscription

by Wally-Ahmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ask_gptA

Ask a GPT model via your ChatGPT subscription. You must choose model explicitly AND write instructions (the model's system prompt) yourself — there are no defaults. Any valid model id is accepted; known suggestions: gpt-5.4 (general), gpt-5.4-mini (faster/cheaper), gpt-5.5 (deepest reasoning — use with reasoning_effort 'high' for architecture, security/threat modeling, and hard review). Treat output as a hypothesis to verify.

check_usageA

Show remaining ChatGPT/Codex subscription quota for the signed-in account.

list_patternsA

List available orchestration patterns for driving the GPT subagents. Call this before non-trivial expert work — reviews, audits, threat modeling, large 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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: ask_gpt for queries, check_usage for quota, get_pattern and list_patterns for orchestration patterns. No overlap in functionality.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (ask_gpt, check_usage, get_pattern, list_patterns), making them predictable and easy to understand.

Tool Count4/5

With 4 tools, the set is concise and focused on core subscription-GPT and pattern orchestration needs. Could possibly benefit from a tool to list available models, but the count is appropriate for its scope.

Completeness4/5

The set covers querying GPT, checking usage, and managing orchestration patterns. A minor gap is the absence of a tool to list models or subscription details beyond quota, but core workflows are well-supported.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources