Select the design patterns to apply to a described system, with per-application language bindings and a traceable reasoning trail. Send the components, their responsibilities and the constraints derived from an architecture result. Returns applications (pattern, participants, implementation steps, bound language variant), supporting patterns, interactions, quality attributes, a test strategy and risks. Use this when the caller wants the generated design; when your agent writes the code itself and only needs the decisions, call analyze_design instead — it runs the same ANALYZE phase and skips generation and evaluation.

Analyze a system description and select design patterns per decision part — the analysis-only path for coding agents that write the code themselves. Returns the repaired design brief, the decision parts with their scope/category hypothesis, and one selection per part (primary pattern, supporting patterns with roles, ranked alternatives, veto ledger, quality-attribute weights that drove the scoring) without generating applications or evaluating them. The selection is a routing decision, not an implementation spec: it carries no participants, implementation steps, code sketches or language bindings — before implementing, call generate_design with this payload to materialize the bound applications without re-running the analysis, or get_design_pattern for each selected pattern when only the catalog record and language bindings are needed. A true is_fallback (payload level, or per part with fallback_reason) marks a selection with no eligible primary — treat it as fallback guidance, not a real match. Use select_design_patterns when the caller wants the generated design.

Materialize the pattern applications for a design: either pass the payload of a prior analyze_design call ('analysis'), or pass explicit catalog pattern names ('patterns') together with the system 'description'. Returns a complete design draft — applications with participants, interactions, implementation steps, code sketches and language bindings, plus interactions, quality attributes, a test strategy and risks. Unknown pattern names raise ERR_003.

Evaluate a design draft against the requirements it must serve: scores 0-100 with per-axis ratings, findings (a 'selection' finding names the offending pattern and drives reselection upstream), and advisory integrity findings of the design itself. Pass the design returned by generate_design or select_design_patterns, plus the requirement text or a prior analyze_design payload.

List all design patterns known to the server. Returns a minimal view with 'name', 'category' and 'description' for each pattern. Optional filters: 'category' (one of: domain-modeling, construction-composition, behavior-selection, interaction-boundary, workflow-messaging, persistence-state, concurrency-resilience, security-verification, specialized-components) and 'language' (one of: generic, c, cplusplus, csharp, go, java, javascript, kotlin, python, ruby, rust, scala, swift, typescript; keeps patterns with a joined implementation for that language).

Get the full JSON of a single design pattern by its name or a resolved alias (e.g. 'singleton', 'borg'). Returns the complete record: intent, problem, context, benefits, tradeoffs, quality_attributes, participants, use cases, related patterns, principles, pitfalls, sources, and the joined per-language implementations with their variants. Raises ERR_013 when the pattern is unknown.

Start a background design-pattern selection job and return a job_id immediately (returns in <100 ms; the job itself takes minutes). ONLY use this when the calling client cannot wait for a long response. After starting, poll get_design_status(job_id) every 10-30 s until status is 'completed', 'failed', or 'cancelled'.

Poll the status of a background design job started with submit_design_job. Returns job_id, status ('pending'|'running'|'completed'|'failed'|'cancelled'), a message and the timestamps; 'result' when completed, 'error' when failed.

Cancel a background design job started with submit_design_job. Best-effort: the job stops at its next stage boundary. Reports the resulting status; a job that already finished is reported as terminal with cancelled=false.

List all available prompts.

Returns JSON with prompt metadata including name, description, and optional arguments.

Get a prompt by name with optional arguments.

Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

List all available resources and resource templates.

Returns JSON with resource metadata. Static resources have a 'uri' field, while templates have a 'uri_template' field with placeholders like {name}.

Read a resource by its URI.

For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in.

Returns the resource content as a string. Binary content is base64-encoded.