Agent Blueprint 2.0
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blueprint_healthA | 检查内置蓝图 Python 引擎、ChatGPT 登录状态和云端模型配置。 |
| blueprint_planA | 启动真实正向蓝图流程：点子/PRD → 需求拆解、五要素、组件选型、架构设计、审稿。返回任务 ID，需轮询 status。使用已登录 ChatGPT 账号调用云端模型。 |
| blueprint_auditB | 启动真实逆向蓝图：扫描指定本机项目并云端推理，生成差距报告和应有 PRD。静态扫描不能证明生产可用。返回任务 ID，需轮询 status。 |
| blueprint_statusA | 查看任务阶段、运行状态、错误、调用/token 用量。completed_draft 表示审稿未通过，必须如实说明。 |
| blueprint_resumeA | 断点续跑已中断/失败任务，校验并复用阶段缓存；累计调用与 token 预算不会重置。 |
| blueprint_resultB | 列出成果路径或读取指定成果正文；必须展示真实审稿结果。 |
| blueprint_cancelA | 取消正在运行的蓝图任务，保留阶段文件。 |
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 7 tools
Each tool maps to a distinct action in the task lifecycle: health (system/config check) vs status (specific task progress), plan (forward workflow) vs audit (reverse workflow), plus resume/result/cancel. The forward-vs-reverse distinction between plan and audit is explicitly described, and health vs status operate on different subjects (engine config vs task state).
All seven tools use the identical blueprint_<verb> snake_case pattern (health, status, plan, audit, resume, result, cancel). No mixing of conventions or casing styles.
Seven tools is well-scoped for an async task orchestration server, covering the essential lifecycle verbs without redundancy or padding. Each tool earns its place.
Coverage is strong: launch (plan/audit), monitor (status), retrieve (result), recover (resume), abort (cancel), and health check. The only minor gap is the absence of a tool to enumerate/list all past tasks, which status/result help work around.