Skip to main content
Glama
HorizunGroup

Horizun PBI MCP

Official
by HorizunGroup

pbi_validate_desktop_render

Checks Power BI report rendering by opening a .pbip/.pbix project, optionally refreshing it, and capturing the actual desktop window to confirm data_loaded is true.

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.

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 (solo .pbip): captura ESA pagina (id o nombre visible), no la que quedo activa. fit_to_page (solo .pbip, activado por defecto): fuerza la vista "Ajustar a la pagina" para que salga el lienzo COMPLETO y no el tercio superior al zoom guardado. Ambos ajustan la vista antes de abrir y la restauran byte a byte al terminar; exigen que el proyecto no este ya abierto (con sesion reutilizada no se pueden aplicar: page falla y fit_to_page degrada a un aviso).

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
NameRequiredDescriptionDefault
pageNo
pathNo
refreshNo
timeoutNo
pbip_pathNo
reuse_openNo
fit_to_pageNo
capture_timeoutNo
refresh_timeout_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations only set readOnlyHint=false, so the description carries the full burden. It explains side effects: opening Desktop, refreshing, closing if it opened, reusing session if already open, restoring model selection, and the data_loaded flag for capture representativeness. No contradictions with annotations.

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 description is long but every sentence carries meaning. It is structured into logical sections: purpose, capture method, parameter explanations, behavior on open/close. It front-loads the core purpose and then details nuances. Slightly verbose but not wasteful.

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

Completeness4/5

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

Given the tool's complexity (9 parameters, .pbip nuances, side effects), the description is thorough. It covers the main use cases, edge cases (session reuse, data_loaded), and behavioral details. It does not explain the output schema in depth, but since output schema exists, that's acceptable.

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

Parameters5/5

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

Schema has 0% description coverage, so the description fully compensates by explaining each parameter: path/pbip_path, page, refresh, fit_to_page, timeout, capture_timeout, refresh_timeout_seconds, and reuse_open. It also explains inter-parameter dependencies (e.g., refresh needed for .pbip data, page requires opening and refresh).

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 description clearly states the tool's purpose: opens a .pbip/.pbix and captures its real window without relying on focus. It distinguishes itself from the PBIR validator by being the visual check that complements it, and from sibling tools like pbi_open_and_refresh by focusing on capture.

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?

It provides context for when to use the tool (visual check, complement to PBIR validator) and when to use refresh, page, and fit_to_page. It explains constraints like requiring the project not already open for page/fit_to_page, but does not explicitly exclude alternatives or say 'use X instead of Y'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HorizunGroup/horizun-pbi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server