pbi-webview2

Overview Schema Source Related Servers Discussions Admin

pbi_set_slicer

Set a slicer value in Power BI reports, supporting button and item slicer kinds.

Instructions

Set a slicer: kind "button" (buttonSlicerVisual, returns aria-pressed before/after) or "item" (list slicer item, returns a fresh state probe).

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": {
      "value": "<value>",
      "kind": "<kind>"
    },
    "name": "pbi_set_slicer"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must disclose all behaviors. It reveals that button kind returns aria-pressed before/after and item kind returns a fresh state probe, but does not mention side effects, destructive potential, or error conditions.

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 description is a single sentence, front-loaded with the action. However, it uses parentheses and could be restructured for clarity. Still, it earns its place with no unnecessary words.

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?

Given two parameters, no output schema, and no annotations, the description provides basic understanding but omits details about return types, error cases, and state changes. It is adequate but incomplete for a full contextual picture.

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 0%, so description must clarify parameters. It explains the 'kind' parameter with its two enum values and the different returns, but fails to describe the 'value' parameter, leaving ambiguity about its format or meaning for each kind.

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 sets a slicer and distinguishes two specific kinds ('button' and 'item'), each with distinct behavior and return values. This provides a specific verb-resource-action and differentiates the tool's two modes.

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 description implies when to use each kind (button vs item) but does not explicitly mention when not to use this tool or compare it to siblings like 'pbi_search_slicer' or 'pbi_click'. Lacks explicit usage context.

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