Skip to main content
Glama
Sign In
pbi-webview2

pbi-webview2

by bibiibjorn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pbi_pages

Retrieve all report page tabs and their active status in Power BI Desktop to identify the current page and navigate between them.

Instructions

List all report page tabs as [{name, active}].

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral aspects such as side effects, permissions, or limitations. For a read-only list operation, the risk is low, but the description fails to add transparency beyond the basic functionality.

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 a single sentence that is concise and front-loaded. It provides all necessary information without any extraneous text, earning a perfect score.

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?

Given the tool's simplicity (no parameters, no output schema), the description is complete. It specifies the action and the output format, meeting all contextual needs for this low-complexity tool.

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?

There are no parameters, so no parameter information is needed. The description does not add any parameter semantics, but the schema coverage is 100% (vacuously). Baseline for zero parameters is 4, indicating no missing information.

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 lists all report page tabs and specifies the output format as an array of objects with 'name' and 'active' fields. It distinguishes from sibling tools like pbi_goto_page (navigation) and pbi_page_sweep (iteration) by focusing on listing.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The tool's simple nature (no parameters, direct output) makes usage intuitive, but it does not mention alternatives or prerequisites, which is acceptable given the low complexity but leaves room for improvement.

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