Horizun PBI MCP

Official

Overview Schema Source Related Servers Discussions Admin

pbi_validate_desktop_render

Destructive

Automates visual verification of Power BI Desktop reports by capturing the actual window after an optional refresh, ensuring .pbip tables and matrices render with data instead of blank visuals.

Instructions

Abre un .pbip/.pbix y captura su ventana real sin depender del foco.

Es la comprobacion visual automatizable que complementa al validador PBIR: espera el modelo, identifica la ventana por PID y hora de inicio, y la renderiza con PrintWindow directamente a outputs/desktop_captures. La captura no activa ni trae Desktop al frente, por lo que no puede fotografiar por accidente otra ventana que tape el informe.

path (o pbip_path, el mismo nombre que devuelve pbi_session_info) se puede omitir: entonces se usa el proyecto .pbip activo.

refresh=true es lo que hace que la captura signifique algo en un .pbip: ese formato guarda la definicion, no los datos, asi que recien abierto el modelo viene VACIO y las tablas y matrices salen en blanco aunque el informe este perfecto. Con refresh se abre, se refresca, se espera a que la ventana deje de repintar y se captura. Ese es tambien el camino para fotografiar OTRA pagina con datos: page exige abrir el proyecto, y al abrirlo hay que volver a refrescar.

Como el refresh modifica de forma irreversible el modelo en memoria, refresh=true exige ademas confirm=true. confirm_reuse autoriza mover una ventana que ya era del usuario; son autorizaciones distintas.

Pase lo que pase, la respuesta lleva data_loaded: si es false, la captura no es representativa del informe, es la foto de un modelo sin datos. Si no se pudo comprobar, se dice; no se afirma ninguna de las dos.

page: captura ESA pagina (id o nombre visible), no la que quedo activa. fit_to_page (activado por defecto): fuerza la vista "Ajustar a la pagina" para que salga el lienzo COMPLETO y no el tercio superior al zoom guardado. Con el proyecto CERRADO (.pbip) ambos se aplican como una vista temporal en disco que se restaura byte a byte al terminar. Con la ventana YA ABIERTA -que es del usuario- se hacen en la propia interfaz, pero SOLO con confirm_reuse=true: elegir una pestaña y cambiar el zoom mueven esa ventana, y una captura que solo debia observar no lo hace por su cuenta. Sin confirm_reuse, page sobre una sesion abierta es un error y fit_to_page degrada a un aviso (se captura al zoom actual). Con el, se elige la pestaña y el zoom por UI Automation y se demuestra el resultado hasta donde se puede (navigation): la pagina por el IsSelected de su pestaña; el zoom solo por el nivel que anuncia Power BI, lo que prueba que el zoom CAMBIO y no que el modo resultante sea "Ajustar a la pagina" -verified_means lo dice en la propia respuesta-. Si la pagina no se pudo demostrar, la tool falla en vez de capturar otra; si el zoom no se pudo demostrar, lo dice en warnings. Nunca toca pages.json de un proyecto abierto.

La captura separa cuatro señales que no son la misma cosa: capture.identity_settled (la ventana muestra ESTE documento), capture.frame_settled (la imagen dejo de cambiar), data_loaded (el modelo tiene filas) y capture.frame_uniform (la imagen es casi de un solo color: pagina vacia o visuales sin pintar). capture.capture_representative resume las tres primeras.

Si la tool tuvo que abrir Desktop, lo cierra al terminar (tambien si la captura falla) y devuelve la seleccion de modelo a como estaba. Si el informe ya estaba abierto, reutiliza esa sesion y nunca cierra la ventana del usuario.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`path`	No
`confirm`	No
`refresh`	No
`timeout`	No
`pbip_path`	No
`request_id`	No
`reuse_open`	No
`fit_to_page`	No
`project_path`	No
`confirm_reuse`	No
`capture_timeout`	No
`refresh_timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Sep 6, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "title": "Confirm",
+  "type": "boolean"
+}

addedInput schema / properties / confirm_reuse

Added value: +{
+  "default": false,
+  "title": "Confirm Reuse",
+  "type": "boolean"
+}

addedInput schema / properties / project_path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Path"
+}

addedInput schema / properties / request_id

Added value: +{
+  "default": "",
+  "title": "Request Id",
+  "type": "string"
+}

Changed7 schema fields changedv2.0.2Aug 19, 2026

addedInput schema / properties / path / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / path / default
```
Added value: +null
```
removedInput schema / properties / path / type
```
Removed value: -"string"
```

addedInput schema / properties / pbip_path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pbip Path"
+}

addedInput schema / properties / refresh

Added value: +{
+  "default": false,
+  "title": "Refresh",
+  "type": "boolean"
+}

addedInput schema / properties / refresh_timeout_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Refresh Timeout Seconds"
+}

removedInput schema / required
```
Removed value: -[
-  "path"
-]
```

Changed2 schema fields changedv1.5.1Aug 12, 2026

addedInput schema / properties / fit_to_page

Added value: +{
+  "default": true,
+  "title": "Fit To Page",
+  "type": "boolean"
+}

addedInput schema / properties / page

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Page"
+}

First observedv1.0.1Aug 3, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Extremely rich disclosure beyond the annotations: refresh irreversibly modifies the model in memory and requires confirm; it closes Desktop if it opened it (even on failure) but never closes a user's window; it restores views byte-by-byte and never touches pages.json; and it fully explains the four capture signals plus the honesty policy around data_loaded. The destructive account is fully consistent with destructiveHint=true — no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, and the bolded refresh explanation makes the single most critical semantic stand out. It is long, but for a 13-param destructive tool with open/closed session modes almost every sentence carries a distinct behavioral fact; only minor redundancy (the never-bring-to-front point recurs) keeps it shy of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 undocumented params, a destructive profile, two session modes, and three distinct authorizations (confirm, confirm_reuse), the description covers purpose, param interactions, side effects, cleanup, failure modes, and response semantics (data_loaded, capture.*, verified_means, warnings). An agent could invoke this tool correctly on the first attempt, and the existing output schema covers the remaining return-value details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage the description carries the full burden and compensates strongly: it explains path/pbip_path aliasing and the omission default, the refresh→confirm coupling, confirm_reuse's distinct authorization, and the page/fit_to_page open-vs-closed behaviors. However, the timeouts (timeout, capture_timeout, refresh_timeout_seconds), project_path, request_id, and reuse_open are left undescribed or only implicit, which are real gaps for an agent tuning a slow capture.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb+resource: opens a .pbip/.pbix and captures its real window without depending on focus. It positions itself as the automatable visual check that complements the PBIR validator, which separates it from the many sibling validation/reporting tools without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use context: it is the visual verification complement to structural PBIR validation, and it explains when refresh=true is mandatory (.pbip stores definitions, not data, so a freshly opened model is empty and would yield blank tables/matrices). It stops short of a 5 because it never explicitly names sibling alternatives or states when-not-to-use exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server