Mql5 Docs Research

Workflow

1. Normalize the error or question into keywords:
   • Extract error code and symbols (function/class names)
   • Keep 2-5 keywords for searching
2. Search Japanese and English docs:
   • Use site search in the docs pages
   • If no direct hit, search broader sections by keyword
3. Open the most relevant doc pages and confirm:
   • Correct function signatures
   • Parameter types and constraints
   • Return values, error handling, and examples
4. Produce a response in Japanese with:
   • Summary of the cause
   • Doc links (JA first, EN second)
   • Specific guidance aligned with doc wording
   • Next checks (if ambiguity remains)

Output Format (Markdown)

• Summary (1-3 sentences)
• Relevant Docs
  • JA: <url>
  • EN: <url>
• Key Notes (bullets)
• Next Checks (bullets, optional)

Guardrails

• If the error cannot be mapped to docs, state that clearly and propose a best-effort hypothesis.
• Never invent API signatures or behavior not documented in the official docs.
• Keep the response concise and actionable.