OWS-GDE-MCP

Validate CIT account-upgrade tickets sitting in the AUTIN approval queue. Reports APPROVE / REJECT / NEEDS_REVIEW per ticket based on attachment rules derived from the requester's USER_EXTRA profile, then awaits user confirmation to execute approval.

Trace and debug end-to-end flows in OWS — page → service, service → service, and page → page navigation. TRIGGER when the user asks "why is X failing", "what's wrong with this page/service", "trace the flow of Y", "audit the call chain", or describes broken behavior in an OWS app. Inspects flow steps, RunScript bodies, input/output schemas, log traces, and reference graph; identifies bad code patterns (silent catch, hardcoded IDs, missing validation), schema mismatches (caller passes X but service expects Y), and dead branches; reports findings with concrete file/step/line locations and recommended fixes.

Capture a reusable OWS/ADC platform finding into the knowledge vault. Use when you confirm a non-obvious, reusable fact about the OWS platform (an API path, a TQL quirk, an auth detail, a service contract) that future sessions should know — so it's recorded once and read first via get_help_home / search_help instead of re-derived.

Decision tree for choosing the right OWS MCP tool. TRIGGER whenever the user asks about OWS, GDE, Huawei tickets, or anything that requires calling an `mcp__ows-gde__*` tool — including queries about tickets (CM, INC, BOT, TTS, CTT), pages, services, models, triggers, scripts, processes, modules, projects, logs, or Studio elements. Use BEFORE making the first MCP call to pick the leanest tool variant and avoid over-fetching.

Checklist and patterns for building a new OWS page element. Use when asked to create or design a page.

Checklist and patterns for building a new OWS service element. Use when asked to create or design a service.

Analyze an OWS Studio page — understand its components, service wiring, and JS behavior. Use when asked to explain, audit, or modify a page element.

Query OWS model data — resolves process prefix, discovers fields, builds and runs TQL. Use when asked about tickets, CMs, INCs, BOTs, or any process data.