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 Visual Sort

pbir_set_visual_sort

Set the sort order of a visual in a Power BI report, overriding auto-sort. Specify fields as Table[Column] with priority and direction.

Instructions

Set the sort order of a visual. Overrides the auto-sort. Use Table[Column] for field refs.

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": {
      "visualId": "<visualId>",
      "sort": "<sort>"
    },
    "name": "pbir_set_visual_sort"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortYesPriority order
pageIdNoPage ID. Auto-resolved when only one page exists.
visualIdYesThe visual ID
isDefaultSortNotrue=user can override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.6

TDQS

A3.8/5.0
Behavior2/5

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

Annotations provide minimal context (openWorldHint: false) and the description does not disclose any behavioral traits beyond the action. It fails to mention side effects, reversibility, or required permissions, which is insufficient for a mutation tool.

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 extremely concise with three short sentences that front-load the main purpose. Every sentence adds value with no superfluous content.

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

Completeness4/5

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

For a simple setter with 4 parameters and no output schema, the description covers the core functionality. It could be improved by noting that existing sort is replaced, but it is largely complete.

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 description coverage is 100%, so the baseline is 3. The description adds 'Use Table[Column] for field refs' which reinforces the schema but does not significantly enrich parameter understanding beyond the existing schema descriptions.

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 'Set the sort order of a visual' using a specific verb and resource, and distinguishes itself from sibling tools that modify other visual properties. It is not a tautology.

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 indicates the tool is used to override auto-sort, providing clear context. However, it does not explicitly state when not to use this tool or mention alternatives, though no direct sibling exists for sorting.

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