Skip to main content
Glama

pbi_health_audit

Return governance, refresh, performance, deleted-dataflow, and architecture findings across all scanned Power BI models.

Instructions

Return governance, refresh, performance, deleted-dataflow, and architecture findings across all scanned Power BI models.

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_health_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
severityNoOptional filter: 'bad' or 'warn'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Return ... findings' signals a read-only aggregate, and the finding categories are disclosed, but there is no mention of cost/latency of auditing all models, permission requirements, pagination, or whether results are truncated.

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

Conciseness5/5

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

A single front-loaded sentence with the resource and scope stated first and the finding categories enumerated compactly. No filler or redundant restatement of the title.

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?

With no output schema and no annotations, the description should say more about return shape and the precondition that models be scanned. It explains what categories of findings come back, which is the essential part, but leaves output structure and scan prerequisites unstated.

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 coverage is 100% and the single optional parameter already documents its accepted values ('bad' or 'warn'), so the baseline is 3. The description adds nothing about what filtering on severity does to the result set (e.g., whether bad-severity findings include warns).

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?

Uses a specific verb ('Return') and enumerates the exact finding categories (governance, refresh, performance, deleted-dataflow, architecture) scoped to 'all scanned Power BI models'. This implicitly distinguishes it from per-model siblings like pbi_inspect_model, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The phrase 'across all scanned Power BI models' implies a fleet-wide audit use case rather than single-model inspection, but there is no explicit when-to-use statement, no prerequisites (e.g., what 'scanned' means or whether a scan must run first), and no stated alternatives.

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