always-okay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to run the HTTP server on | 8000 |
| RATE_LIMIT | No | Requests per minute per IP | 120 |
| ALLOWED_HOSTS | No | Public hostname; enables DNS-rebinding protection |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_frameworkA | Overview of the lens: the Frame → Make → Edit → Deliver loop, the eight stages and every principle's id, title, status and evidence support. Call first when starting creative work. |
| get_principleA | Full text of one principle (e.g. 'P08'): the rule, its limits, what it guards against, known tensions, evidence support and the claim IDs behind it. |
| search_evidenceA | Search the evidence notes (paraphrased statements with source and locator). Filter by free text, optional domain (e.g. 'launch', 'brand', 'collaboration'), optional era (E0–E8 or 'cross'). Use to answer 'what is the evidence for…'. Returns at most |
| traceA | Trace a principle (P##) or claim (MHJ-CL-###) down to its evidence notes and public sources. Use when the user asks why a recommendation holds or where it comes from. |
| list_tensionsA | Documented tensions, contradictions and myths the lens keeps open (e.g. retro rejected as a target vs a nostalgic record; creative–management integration vs 'not universal'). Pass a principle id to get only its tensions, or a text query. |
| get_modeB | Working mode guide. Modes: STRATEGIST, CREATIVE DIRECTOR, PRODUCT, BRAND ARCHITECT, COPY / EDITOR, CRITIC, EXECUTIVE, LAUNCH DIRECTOR, REFERENCE CURATOR, FULL DIRECTOR. Empty = list all. |
| get_checklistB | Return a working checklist as text: 'brief' (brief interrogation), 'concept', 'signature' (signature device test), 'edit' (critique pass), 'launch', 'briefing' (briefing a specialist), 'conventions', 'taste', 'language' (copy rules KO/EN) or 'limits'. |
| check_draftA | Deterministic lint for a creative draft (no model call): flags declared quality/benefit words, buzzword filler, template phrasing, borrowed aesthetic tropes and any wording that speaks as or for Min Hee-jin. Reports only; never edits. Works for Korean and English. |
| searchA | Search the always-okay lens (principles, evidence notes, tensions, checklists) for creative-direction guidance. Returns result ids to pass to |
| fetchA | Fetch the full text of one always-okay document by the id returned from |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| creative_direction | Start a creative-direction session with the lens on a brief. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct roles: get_framework, get_principle, list_tensions, get_mode, get_checklist, and check_draft target different artifacts. Some overlap exists between search/search_evidence/trace and between fetch and the specific get_* tools, but the descriptions provide enough workflow guidance to avoid most misselection.
The names use consistent snake_case, and get_* is applied predictably to direct resource retrievals. A few tools are bare verbs (trace, search, fetch), which is a minor deviation but still readable and coherent.
Ten tools is well-scoped for a creative-direction knowledge base with principles, evidence, tensions, modes, checklists, and draft linting. Each tool appears to earn its place without obvious redundancy.
The surface covers the core lifecycle: overview, principle detail, evidence search and tracing, tensions, mode guides, checklists, draft linting, and generic search/fetch. Minor gaps exist, such as no explicit enumerate-all command for checklists, but they are workable through search or known checklist names.