--- title: Tools description: Every agent tool the devtools expose, grouped by inspector, with what it answers and its arguments. --- One hundred and two tools, grouped by inspector. Each one answers a question you would otherwise answer by clicking through the panel. # Tools This page lists every tool the [MCP server](./mcp-server.md) exposes. Each group matches an inspector in the panel. The server's [prompts](./mcp-server.md#prompts) chain these tools into ready workflows, such as `debug-error` and `fix-form`. ## Before you call a tool ### Names Tool ids use a colon, as `pangular:scan-routes`. MCP clients see them with an underscore, as `pangular_scan-routes`. The tables below drop the `pangular:` prefix. The `read` tools are also registered on the page under the same names, for [browser agents](./browser-agents.md). Each tool has a short title that clients show in their tool lists. Every tool answers with one plain text block: markdown, or compact JSON for a source scan. See [Titles and answers](./mcp-server.md#titles-and-answers). ### Source and live tools Each tool reads from one of three places. The stdio server registers only the tools that read your source, because no page reaches it. Reads your files. Works over stdio and HTTP, with or without a browser. Reads what a connected page reported. Needs the HTTP endpoint and the app open in a browser. Reads what the Vite dev server recorded. Needs the Vite plugin. ### Analog, Capacitor and TanStack Query tools The `analog-` tools, `capacitor-list-calls`, `capacitor-list-plugins`, `tanstack-list-queries`, `tanstack-inspect-query` and `tanstack-run-query` are listed only when the app uses the library: the project's `package.json` lists `@capacitor/core` or an `@tanstack/angular-query` package, the project is an Analog app, or a page reports the library's data. In the last case the server adds the tools and sends `notifications/tools/list_changed`. A client that doesn't follow it sees them when it reconnects. Setting `inspectors.` or `agent.tools.` in the [configuration](../getting-started/configuration.md#inspectors-and-agent-tools) turns them on or off for good. If the server can't read a `package.json`, it lists them all. ### A wrong project folder If the server scans a folder with no Angular project in it (no `angular.json`, and no `package.json` that depends on `@angular/core`), every source tool refuses with `isError: true` and names the folder, instead of answering an empty list. Restart the server with `--root` or `PANGULAR_ROOT` set to the project folder. See [Connect over stdio](./mcp-server.md#connect-over-stdio). ### The page argument Most page tools take an optional `page` argument to pick a browser tab. Without it, every tool reads the same default page: among the tabs that report the tool's data, a tab in the foreground before one in the background, then the tab that connected last. `list-pages` lists pages in that order, so its first row is the default page. The answer names the page it read on its first line (`Page .`), unless its text or JSON already names it. Some calls name their page another way: | Call | Page | | -------------------------------------------------------- | ----------------------------------------------------------------------- | | `run-form-action`, `fill-form`, a form tool given `form` | The tab in the form id (the part after `@`, as in `Checkout.form@ab12`) | | `set-signal`, `set-component-property` | The one tab that has the instance `component` names | | `ngrx-inspect-store`, `ngrx-history` given `store` | The tab of that store | | `highlight`, `inspect-component` given `component` | Every tab is searched for the instance, default page first | | `defer-blocks`, `for-blocks`, `hydration` | Every tab is listed | Tools that change app state never pick one of several tabs on their own: `navigate`, `probe-route`, `record-guards`, `ngrx-dispatch`, `ngrx-restore`, `ngrx-store-devtools`, `tanstack-run-query`, `set-signal` and `set-component-property` refuse and list the tabs when more than one could take the call. The tables below leave `page` out. If `page` names a tab that doesn't report that data, the tool answers `No page is reporting ...` and lists the tabs that do. It never falls back to another tab. A `page` that is not a string, such as a number, is refused the same way, and an empty string counts as left out. `page` is the only page argument: a call that sends `pageId` is refused. ### Arguments and refusals The server checks each call's arguments against the tool's input schema before the tool runs: types, required arguments, allowed values and ranges. A wrong argument is answered with `Invalid arguments:` and a line for each argument that names what it takes, as in `` `limit` must be at most 50, not 1000000. ``. A `null` for an optional argument counts as left out. The argument names are the same in every tool: | Argument | What it names | | ----------- | ----------------------------------------------------------------------------------- | | `page` | A page id from `list-pages` | | `component` | A component instance: an instance id, a class name or a host tag | | `selector` | A CSS selector, and nothing else | | `injector` | An injector: an environment injector name such as `Root`, a tag, a class or an id | | `node` | A signal graph node, by id or label | | `property` | A field on a component: an input, a property or a signal | | `store` | A store, by id or name | | `after` | A point in a log: a forms marker or an NgRx `seq`. Only entries after it are listed | | `since` | A point in time: a duration back from now such as `30s`, a date, or epoch ms | A call that sends an argument name a tool no longer takes, such as `selector` for `inspect-component` or `storeId` for `ngrx-history`, is refused with the name to use instead. An argument that moved to another tool is refused with the tool to use: `record`, `flash`, `track` and `angularProfiling` on `change-detection` (use `record-change-detection`), `overlay` on `hydration` (use `highlight` with `hydration`), and `routeId` and `on` on `navigate` (use `list-routes` with `resolveLazy`, and `record-guards` with `on`). A tool that refuses a call answers with `isError: true`. That covers a wrong or missing argument, a `page` that reports no such data, an action turned off in the config or under `agent.readOnly`, a form or action the page refuses, and a write that would have to guess the tab. The text starts with `Refused:` or `Invalid arguments:` and says what to change. An action or destructive tool that does nothing also answers `isError: true`: no page to send it to, a target that matches nothing, a navigation the app cancelled or that failed, or a recording no page confirmed. An empty result of a read, such as no HTTP calls yet, is an ordinary answer. Tools that start or stop a recording (`record-change-detection`, `record-pipes`, `track-subscriptions`) wait up to 3 seconds for each page to confirm, and name the pages that did. ### Older Angular versions When the page's Angular lacks the debug API a tool needs, the tool answers **Unsupported on this Angular version** with the version the feature needs and the version the page runs, instead of an empty list. `inspect-signals`, `watch-signal`, `defer-blocks`, `for-blocks`, `change-detection` and `diagnose-change-detection` answer this way. `inspect-providers` puts the same note before a reduced tree. See [Supported Angular versions](../getting-started/installation.md#supported-angular-versions). ### list-pages Lists the tabs, [Angular Native](../getting-started/angular-native.md) apps, [NativeScript](../getting-started/nativescript.md) apps and [Capacitor](../guides/capacitor.md) apps that report to the server, default page first (see [The page argument](#the-page-argument)): page id, URL, title, platform (`browser`, `Angular Native`, `NativeScript`, or `Capacitor (android)` and `Capacitor (ios)` for an app in a native WebView, followed by the page's Angular version when it reported one, as in `browser, Angular 15.2`), seconds since the last report or heartbeat, and which inspectors report. Takes no arguments. Reads: page. Use it to find the id to pass as `page`. The URL comes from the HTTP or router report. A page that sends neither (no router, and no [HTTP setup](../getting-started/express.md)) still shows the URL its component tree reports, which also stands in when the other reports are more than 30 seconds older. A tab in the background stops reporting until it is shown again, so its last report is marked `(background)`: an old time there means the data is the last known state, not that the page is gone. A tab that closes leaves the list at once. A tab that crashes or is killed without closing leaves it, with all its data, 30 seconds after its last report or heartbeat. ### snapshot Gives one page's full picture in one bounded markdown answer, for an agent that wants everything at once or a bug report. Reads: page. Each section comes from the tool named under its heading, with the same masking, so call that tool for the rest. | Section | What it holds | Full answer | | ------------- | ---------------------------------------------------------- | ----------------------- | | `page` | Page id, URL, title, platform, Angular version, inspectors | `list-pages` | | `components` | The component outline | `list-components` | | `route` | The URL and the active route tree | `inspect-route` | | `navigations` | Recent navigations, one line each, newest first | `explain-navigation` | | `http` | HttpClient calls, newest first | `list-http-calls` | | `errors` | Error groups, most recent first | `list-errors` | | `console` | Console calls, newest first | `list-console` | | `forms` | Each form with its status and error count | `inspect-forms` | | `signals` | The signal graph, without Angular's own nodes and history | `inspect-signals` | | `stores` | NgRx stores and Redux DevTools stores | `ngrx-inspect-store` | | `queries` | TanStack Query queries and mutations | `tanstack-list-queries` | | Argument | Required | What it is | | ---------- | -------- | ---------------------------------------------------------------------- | | `sections` | No | The sections to include, in the order above. Every section without it. | | `limit` | No | Most items per section, 1 to 50 (default 10). | | `maxChars` | No | Longest answer, 2,000 to 50,000 characters (default 20,000). | Each section is also cut at 4,000 characters. When the answer reaches `maxChars`, it ends with a `Truncated` note that names the sections left out. A section whose inspector is off in `inspectors`, or whose tools are off in `agent.tools`, is listed under `Skipped`, and a section the page reported nothing for is listed as empty. The answer starts with the untrusted-data notice once, for every section. ### open-in-panel Gives the user a link that opens the panel on one tab with one item selected, and switches the panels that are open to it. Reads: page. Use it to point the user at what you found. | Argument | Required | What it is | | -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `tab` | Yes | The tab: `dashboard`, `timeline`, `audit`, `components`, `routes`, `signals`, `injectors`, `store`, `queries`, `forms`, `pipes`, `network` (SSR & HTTP), `errors`, `analog`, `capacitor` or `plugins`. Only tabs that are on count. | | `id` | No | The item to select: a component id on `components`, the id of the component whose element injector to show on `injectors`, a form id on `forms`. Other tabs ignore it. | | `page` | No | The page the item belongs to, from `list-pages`. | The answer is a full URL, such as `http://localhost:4200/__devframes/pangular/#tab=components&id=12&page=k3x9`, when the hub serves the panel and a page has reported its address. Otherwise it is the hash to add to the panel's address. Each panel that is open and not in a background tab opens the link at once. The tool is `read`: it changes what the panel shows, not the app. See [Deep links](../getting-started/popup-and-hub.md#deep-links). ### wait-for Waits until a condition holds on a page, then answers. Use it after a click, a navigation or an action instead of calling another tool in a loop. Reads: page. It reads what the collectors already reported and never changes the page. It answers as soon as the condition holds, or after `timeoutMs` with `Timed out after ms` and the last state it saw. | Condition | Holds when | Argument | Inspector | | ---------------- | ----------------------------------------------------------------------------------------- | ------------------------ | ---------- | | `component` | A component matching `component` is rendered. | `component` (required) | Components | | `component-gone` | No component matches `component` any more. | `component` (required) | Components | | `navigation` | The router has no navigation in progress, and its URL matches `url` when given. | `url` | Router | | `http-call` | An HttpClient call finished after the wait started, and its URL matches `url` when given. | `url` | SSR & HTTP | | `error` | A new error was captured after the wait started, with the Angular code `code` when given. | `code`, such as `NG0100` | Errors | | `form` | A form is `settled` (default), `valid`, `not-pending`, or `submitted` after a marker. | `form`, `until`, `after` | Forms | | Argument | Required | What it is | | ----------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- | | `condition` | Yes | One of the conditions above. | | `component` | No | An instance id, class name or host tag, as in `highlight`. | | `url` | No | Text the URL contains. `*` matches anything and a leading `^` anchors it at the start of the path, as in [fault rules](#fault-rules). | | `code` | No | An Angular error code. | | `form` | No | A form id or label from `inspect-forms`. Every form without it. | | `until` | No | For `form`: `settled` (no pending async validation, debounce or submit in flight), `valid`, `not-pending` or `submitted`. | | `after` | No | For `form` with `until: "submitted"`: a marker from a forms answer. | | `timeoutMs` | No | How long to wait. Default 5000, at most 30000. | | `page` | No | The page id. Without it, every page counts, and `navigation` uses the most recent page. | Without `url`, `navigation` holds as soon as no navigation is in progress, which can be before a navigation you just started reaches the page. Pass `url` to wait for the destination. A condition is offered only while its inspector is on for agents, and the tool is dropped when all five are off. ### Action tools Every tool has one of three safety tiers. The server sends the tier to your client as the tool's read-only and destructive hints. | Tier | What the tool can do | Tools | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `read` | Reads your source, the page or the server. `highlight` only shows and selects a component. | Every other tool, and every resource | | `action` | Changes the running page, the server's fault rules and SSR overrides, or what the page records. A reload or the next call undoes it. | `navigate`, `probe-route`, `record-guards`, `ngrx-dispatch`, `ngrx-restore`, `ngrx-store-devtools`, `tanstack-run-query`, `run-form-action`, `fill-form`, `set-http-rule`, `remove-http-rule`, `set-ssr-override`, `remove-ssr-override`, `set-component-property`, `set-signal`, `watch-signal`, `record-pipes`, `track-subscriptions`, `record-change-detection` and `audit` | | `destructive` | Can lose data: it erases recordings, or sends writes to your own API routes. | `clear-recordings` and `analog-run-api` | The twenty-two action and destructive tools act on the app. Your client can ask you before it runs them. When the hub is mounted, each finished call of an `action` or `destructive` tool posts an `Agent ran ` message to the hub, so you can see what the agent changed. `record-change-detection` posts only when it starts, stops or clears a recording, or turns a live view on or off, and `audit` only when it runs axe. See [Messages and badges](../getting-started/popup-and-hub.md#messages-and-badges). ### Turn tools off The server decides which tools exist. Set `agent.readOnly` to keep only the `read` tools. `change-detection` reads a recording the panel started, and its hints, like those of `diagnose-change-detection` and `audit`, name only **Record** in the panel. `audit` stays without its `axe` argument, so it reads the last axe pass the panel ran. Set `agent.tools.` to `false` to hide one inspector's tools and resources, and keep its tab. Turning an inspector off with `inspectors`, or blocking an action with `actions`, drops the matching tools too. `wait-for` stays while any of the Components, Router, SSR & HTTP, Errors and Forms inspectors is on, with only the conditions of the inspectors that are. A [plugin's own tools](#plugins) follow the same switches, with the tier the plugin declares. `actions.router` drops `navigate` and `probe-route` and keeps `record-guards` and `list-routes` with `resolveLazy`. See [Inspectors and agent tools](../getting-started/configuration.md#inspectors-and-agent-tools). ## Source scan These seven tools read your source and answer compact JSON. Every tool that reads only your files starts with `scan-` (after its library prefix, as in `ngrx-scan` and `analog-scan-routes`). | Tool | What it answers | Arguments | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------- | | `scan-routes` | Angular routes from your route files, with full URL path (parents and `loadChildren` prefixes included), kind (page, group, redirect or wildcard), guards, resolvers, and file and line. | None | | `scan-components` | Components and directives from `@Component` and `@Directive` classes, with class name, selector, kind, inputs, outputs, change detection (components only), and file and line. | `filter`, `offset`, `limit` | | `scan-signals` | `signal()`, `computed()`, `linkedSignal()`, `effect()`, `toSignal()` and resource declarations (`resource`, `httpResource`, `rxResource`), plus signal inputs, models and queries. | `filter`, `offset`, `limit` | | `scan-providers` | DI providers: `@Injectable` services, `inject()` calls, constructor parameters and `providers` arrays, with token, file and where each one is provided. | None | | `ngrx-scan` | NgRx declarations: `@ngrx/store` actions (with their type strings in `types`), reducers, effects, selectors, features and store setup, and `@ngrx/signals` `signalStore` (with its members), `signalState` and `signalMethod`. | None | | `scan-pipes` | Custom `@Pipe` classes, and built-in pipes from `@angular/common` in use in templates, with purity, standalone status, and where each is declared or used. | None | | `scan-build` | The project name, the Angular and TypeScript versions, SSR status, the Analog version in Analog apps, and a `builtAt` timestamp. | None | `scan-components` and `scan-signals` answer at most `limit` items (default 200, at most 1,000) and at most 20,000 characters. A list that fits is the JSON array alone. A cut list is followed by a note with the items shown, the total and the `offset` of the next part, such as `Showing signals 1-200 of 450; 250 more not shown. Pass offset: 200 for the next part`. An item longer than 20,000 characters on its own is cut, so that answer is not valid JSON. Its note gives the `offset` of the next item. `filter` keeps the items whose fields contain the text, in any case: class name, selector, kind and file for components, and name, kind, file and component for signals. ## Components, signals and DI ### highlight Highlights a component in the page, scrolls it into view, selects it and makes it the target of `inspect-signals`. The `component-tree` resource then carries its live `detail`, and the Components tab selects it too. Reads: page. | Argument | Required | Value | | ----------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `component` | one of | An instance id from the `component-tree` resource (like `c12`), a class name or a host tag. | | `selector` | one of | A CSS selector. | | `hydration` | one of | `true` outlines the hydrated, skipped, mismatched and dehydrated regions of a page rendered on the server, with a label on each and a legend. `false` removes the outline. | Pass exactly one of the three. An instance id targets that exact instance, for example the second card of a list. A class name or tag that matches several instances picks the first and lists the ids of all of them. A `component` that matches no instance is refused, not sent on as a CSS selector. A CSS selector highlights but doesn't change the selection. With `page`, a CSS selector or the hydration outline goes to that tab only. The hydration outline draws in its own layer over the page, ignores the pointer and changes nothing in the app. It is the **Outline on page** button of the [Hydration](../inspectors/components.md#hydration) section. ### inspect-component The live detail of one component instance: inputs, outputs and whether a parent listens, other own properties (signals and resources unwrapped), DOM listeners, host directives, change detection, encapsulation, host path and injected services. It selects the instance on its page and waits up to 3 seconds for the page to report it. Reads: page. | Argument | Required | Value | | ----------- | -------- | ---------------------------------------------------------------------------- | | `component` | yes | An instance id from the `component-tree` resource, a class name or host tag. | | `path` | no | One value to read instead of the whole detail, such as `user.address`. | | `depth` | no | With `path`: levels to read below it, 1 to 5. Defaults to 1. | | `limit` | no | With `path`: most entries per object or list, 1 to 1000. Defaults to 30. | A class name or tag that matches several instances answers for the first and lists the ids of all of them. A class name or tag only finds components. The id of a directive host from `list-components` answers with the directives on that element, since it has no component detail. When nothing matches and the page's tree stopped at a [limit](../inspectors/components.md#selection), `inspect-component` and `highlight` say which one, since the instance can be past it. Secret-looking values are redacted. Each value in the detail shows its first level. A nested object, array, `Map` or `Set` reads `{"$collapsed": type, "size": n}`, and a list cut at 30 entries ends with a `$more` count. Pass `path` to read that value: an input or property name, then keys and indexes, as in `user.address` or `items[0]`. An index into a `Map` or `Set` counts its entries. With `path`, the tool reads the value without changing the selection. It reads own data properties only, so getters never run, and it refuses a path through a redacted name. Each input and property carries `editInside` when a path inside it can be written with `set-component-property` or `set-signal`. The answer stops at 20,000 characters. Past that, each value longer than 1,000 characters shows only the start of its JSON, then each list (inputs, outputs, properties, listeners, directives, injected services, and the inputs and outputs of each directive) keeps fewer entries. A note names the cut values and says how many entries are not shown. The `detail` of the `component-tree` resource has every value in full. ### list-components The live component tree of one page as an indented outline, one line per instance: class name, host tag and instance id, as in `ProductCard c12`. An element that hosts directives but no component gets a line too, as in ` [routerLink] c14 [directive host: RouterLink]`. Reads: page. | Argument | Required | Value | | ---------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `filter` | no | A search, as in the [Components](../inspectors/components.md#search-syntax) filter: plain text, `` and `[directive]`, such as `