MCP Tools
Context Intelligence

trigger_health_audit_scan

Start a library-wide Context Intelligence health audit — an AI sweep of your context/reference items that produces findings. Consumes credits, plan-gated (Business/Command), runs in the background.

Input Schema

{
  "type": "object",
  "properties": {}
}

Output Schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "running"
    },
    "message": {
      "type": "string"
    },
    "scan_run_id": {
      "type": [
        "string",
        "null"
      ],
      "format": "uuid"
    }
  }
}

Instructions

Start a Context Intelligence health audit — a library-wide AI sweep of your team’s context/reference items that produces findings (stale content, contradictions, gaps) reviewable via list_ci_findings.

Use this when the user explicitly asks to check/audit their context health (“run a health check on our context”, “scan the library”). Do not trigger one unprompted — always confirm first.

⚠️ Cost + gating: the scan consumes team Studio Credits and is gated. It requires the Command plan (active subscription) with at least 50 credits remaining. Only one health audit can run at a time, and a cooldown applies after each completed run (the error message tells you when it can run again). Starting a new audit clears the previous health-audit findings.

The scan runs in the background: the response returns immediately with a scan_run_id, and findings land as the scan progresses — check list_ci_findings afterwards.

Errors:

  • ci_not_eligible (403) — plan/subscription/credits gate failed (JSON error body with reason + credit numbers).
  • A health check is already running. Please wait for it to finish.
  • Health check ran recently. You can run it again in about {time}.

Example prompts:

  • “Run a health check on our context library.”
  • “Audit our reference docs for anything stale or contradictory.”
Scroll to Top