Skip to main content
Glama

pbi_report_layout

Inspect Power BI report visual layouts, pages, visual groups, slicer selections, report-level thin DAX measures, and broken visual bindings.

Instructions

Inspect Power BI report visual layouts, pages, visual groups, slicer selections, report-level thin DAX measures, and broken visual bindings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pbi_report_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportNoOptional report name or report GUID filter (omit to list all scanned reports).
include_visualsNoInclude per-page visual items and field bindings (default: true).
redact_literalsNoScrub filter literals, slicer selections, and free-text boxes (default: false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it does not say whether inspection is read-only, where the data comes from, or what a result looks like. The mention of slicer selections and broken bindings hints at the output content, and 'redact_literals' implies sensitive literals are surfaced by default, but permissions, cost, and failure modes are unaddressed.

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?

A single front-loaded sentence with no filler; every noun in the list is a real inspection category. The dense enumeration is slightly hard to parse but costs nothing in length.

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

Completeness3/5

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

For a three-parameter tool with no annotations and no output schema, the description covers what can be inspected but not how results are shaped or whether visual data is returned inline versus summarized. It is adequate to select the tool, marginally adequate to predict its response.

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

Parameters3/5

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

Schema description coverage is 100%, with all three parameters documented in-schema including defaults and the omit-to-list-all behavior, so the baseline is 3. The description adds no parameter-level meaning beyond naming the artifact categories those flags control.

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

Purpose4/5

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

The description uses a specific verb, 'Inspect', with a concrete resource, Power BI report visual layouts, and enumerates the artifacts covered (pages, visual groups, slicer selections, report-level thin DAX measures, broken bindings). It gives a clear picture of scope, though it never contrasts itself with the nearest sibling, pbi_inspect_model, or states that it operates on reports rather than semantic models.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus pbi_inspect_model, pbi_health_audit, or pbi_catalog_summary, and no stated prerequisites such as needing a prior scan or an exported report file. The 'report' parameter's filter behavior is left entirely to the schema.

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