Skip to main content
Glama
Sign In
Power BI Report MCP Server

Power BI Report MCP Server

by jonathan-pap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Report

pbir_set_report

Switch to a different Power BI report mid-session by providing the path to the .Report or .pbip project folder, without restarting the server.

Instructions

Connect to a different Power BI report (.Report folder or parent .pbip project folder). Use this to switch reports mid-session without restarting the server.

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": {
      "path": "<path>"
    },
    "name": "pbir_set_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the .Report folder or the parent folder containing a .pbip project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.6

TDQS

A4.1/5.0
Behavior3/5

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

Annotations only include openWorldHint: false, which is not contradicted by the description. The description adds context about switching reports but does not disclose additional behavioral traits such as whether it requires specific permissions or what happens to current state. Given minimal annotations, this is adequate but not exceptional.

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?

The description is two sentences, front-loaded with the key action, and contains no unnecessary words. Every sentence serves a clear purpose.

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?

For a simple tool with one parameter and no output schema, the description gives enough context: what the tool does, when to use it, and what input is expected. No additional details are needed.

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% with the 'path' parameter fully described in the schema. The description repeats the path requirement but adds no new semantic details beyond what the schema provides, so baseline score of 3 is appropriate.

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: 'Connect to a different Power BI report'. It specifies the resource type (.Report folder or .pbip project) and distinguishes itself from siblings like pbir_get_report by indicating it switches reports mid-session.

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?

The description provides explicit usage guidance: 'Use this to switch reports mid-session without restarting the server.' It gives a clear context but does not mention when not to use it or alternatives, though the use case is well-defined.

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

Deploy Server

Other Tools