pbi-webview2

Overview Schema Source Related Servers Discussions Admin

pbi_dialog

Automates Power BI Desktop dialogs by reading their content or clicking buttons, with safety checks to prevent accidental saves.

Instructions

Automate a Desktop dialog (desktopDialogHost CDP target — exists ONLY while a dialog is showing). action:"read" returns {open, text, buttons}; action:"click" trusted-clicks the button matching button (exact, then case-insensitive contains). Returns {open:false, reason:"no dialog showing"} when none is up. SAFETY: a button labelled "Save" (any case) is refused UNLESS the button param is EXACTLY "Save" (case-sensitive) — protects against accidentally saving the report.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "pbi_dialog"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`button`	No	Label to click (required for action:"click")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Explains actions, return values, and a safety rule about 'Save' button. Transparent about click matching behavior.

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?

Well-structured with sections for actions and safety. Slightly verbose but every sentence adds information. Front-loaded with purpose.

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?

Covers both actions, required parameters, return values for success and failure, and safety constraints. No output schema but return values are described.

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?

Schema coverage 50% only documents action enum and button label. Description adds matching strategy (exact then case-insensitive contains) and safety rule, providing value beyond schema.

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?

Clearly states it automates a Desktop dialog with specific actions 'read' and 'click'. Distinguishes itself from siblings by mentioning the CDP target and dialog-only existence.

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?

Explicitly says when to use (dialog showing) and what happens when not ('no dialog showing'). Does not mention alternatives among siblings, but no other dialog tool exists.

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