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 Page Background

pbir_set_page_background
Idempotent

Set the background color and wallpaper for a Power BI report page. Adjust transparency for both canvas and wallpaper.

Instructions

Set the page canvas background and/or wallpaper. Hex color (#0D1117). Transparency 0-100.

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": "pbir_set_page_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoRemove all background/wallpaper settings
colorNoCanvas background color (hex)
pageIdNoPage ID. Auto-resolved when only one page exists.
transparencyNo
wallpaperColorNoColor behind the canvas
wallpaperTransparencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.6

TDQS

B3.3/5.0
Behavior2/5

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

Annotations provide idempotentHint=true and openWorldHint=false, but the description adds no extra behavioral information (e.g., side effects, permission needs, interplay between color and wallpaper parameters). Safety profile is not expanded beyond 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 single sentence is very concise, but it lacks structure (e.g., bullet points for parameters). Nevertheless, it efficiently conveys core purpose with minimal verbosity.

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

Completeness2/5

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

With no output schema and 6 optional parameters, the description fails to integrate parameter details or explain what happens on execution (e.g., how clear interacts with color, return state). A more comprehensive description is needed for adequate contextual completeness.

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?

The description supplements schema with a hex example (#0D1117) and transparency range (0-100), compensating for the 2 parameters lacking schema descriptions. However, it does not explain parameter interactions or default behavior.

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 verb 'Set' and the resource 'page canvas background and/or wallpaper', specifying accepted value formats (hex color, transparency range). It also implicitly distinguishes from sibling tools since no other tool addresses background settings.

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?

The description provides no guidance on when to use this tool versus alternatives like pbir_apply_theme or pbir_set_report_theme, which also affect background. No when-not, prerequisites, or context for use.

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