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

MCP Server for Power BI

by Mitsubishi-Fuso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

execute_dax_query

Execute DAX queries against Power BI datasets to retrieve and analyze table data. Requires workspace and dataset IDs, and a query starting with EVALUATE.

Instructions

Execute a DAX query against a dataset.

This tool executes DAX (Data Analysis Expressions) queries against Power BI datasets. DAX queries must use the EVALUATE keyword for table expressions.

Args: workspace_id: The unique identifier of the Power BI workspace (UUID format). dataset_id: The unique identifier of the dataset (UUID format). dax_query: The DAX query text to execute. Must start with EVALUATE for table queries.

Returns: Query results with tables and rows, or error information if the query fails.

Common errors:

  • 400 Bad Request: DAX syntax errors, invalid table/column references

  • 403 Forbidden: Missing permissions or tenant setting not enabled

  • Limitations: Max 100,000 rows or 1,000,000 values per query

Example DAX query: EVALUATE TOPN(10, 'Sales')

Raises: ToolError: If parameters are invalid or query execution fails

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": {
      "workspace_id": "<workspace_id>",
      "dataset_id": "<dataset_id>",
      "dax_query": "<dax_query>"
    },
    "name": "execute_dax_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
dax_queryYes
dataset_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses common errors, limitations (max rows/values), and that query must start with EVALUATE. Does not explicitly state idempotency or read-only nature, but provides substantial behavioral context.

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?

Well-structured with clear sections (Args, Returns, Errors, Example). Slightly verbose but front-loaded with purpose. Each section adds value.

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 complexity of DAX query execution and lack of annotations, the description is complete: covers parameters, errors, limitations, and example. Output schema exists but description adequately describes return types.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description thoroughly explains each parameter: workspace_id/dataset_id as UUIDs, dax_query must start with EVALUATE. Includes example, adding significant meaning beyond the schema.

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 executes DAX queries against Power BI datasets, using specific verbs and resource. It distinguishes itself from siblings which are about listing workspaces/datasets.

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 usage for executing DAX queries but does not explicitly state when not to use it or provide alternatives. However, siblings are clearly distinct, so confusion is minimal.

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