# get_flight_viz_guide
> Load the Flight Explainer convention, the chart and progress lines that make a Flight's runs viewable step by step.
Loads the guide to the [Flight Explainer](/key-tasks/flights/observability/explain-flight-runs) convention: the Mermaid chart a Flight declares and the `@flight-run` and `@flight-log` lines it prints, so its runs can be viewed step by step with per-step status and timing. An AI agent calls it first whenever you ask the agent to visualize, chart, watch, or review a Flight's progress.

## Description

`get_flight_viz_guide` returns the full Flight Explainer guide, or one section of it for a narrow lookup. Your AI agent loads the whole guide when it adds or changes instrumentation, adds fan-out, branches, child Flights, timing, or progress, or interprets a nontrivial run, because those tasks span sections.

## Input parameters

| Parameter | Type | Required | Description |
|---|---|---|---|
| `section` | string | No | Load one section only: `chart` (Mermaid declarations, node kinds and meters, labeled edges, child-Flight nodes), `grammar` (`@flight-run` and `@flight-log` events, fields, effects, JSON mode, status roll-up, branches), `emitting` (Python `print` and helper patterns), or `examples` (a worked Flight). Omit to load the whole guide. |

## Output

The tool returns JSON with `success` and the `guide` text. A single section ends with a note on what the excerpt leaves out.

## Example usage

```text
Add a Flight Explainer to the orders_nightly Flight without changing what it does.
```

The AI agent calls `get_flight_viz_guide`, reads the Flight with [`get_flight`](../get-flight), adds the chart and progress lines to its source with [`edit_flight_source`](../edit-flight-source), and opens the next run with [`view_flight_run`](../view-flight-run).

## Related

- [Watch Flight run progress with the Flight Explainer](/key-tasks/flights/observability/explain-flight-runs) — the human-readable version of the convention, with examples.
- [`get_flight_guide`](../get-flight-guide) — The general Flight authoring guide.
- [`view_flight_run`](../view-flight-run) — Open a run in the Flight Explainer.


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fsql-reference%2Fmcp%2Fflights%2Fget-flight-viz-guide%2F&page_title=get_flight_viz_guide&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.