PowerBI Analyst MCP

Overview Schema Source Related Servers Discussions Admin

list_tables

Retrieve visible table names from a Power BI dataset to identify available data structures for analysis, measure listing, and DAX query execution.

Instructions

List all visible tables in a Power BI dataset.

Hidden tables and internal Power BI system tables (names starting with '$') are excluded. Use the returned table names in list_measures, list_columns, and DAX queries.

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>"
    },
    "name": "list_tables"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	Yes
`dataset_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Mar 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses filtering behavior (excludes hidden tables and system tables prefixed with '$'), but omits safety properties (read-only status), rate limits, or pagination behavior that would be expected for a data retrieval 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?

Three well-structured sentences with zero waste: purpose declaration, behavioral constraints (filtering), and usage guidelines (chaining). Information is front-loaded and every sentence earns its place.

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 the tool has an output schema, the description appropriately does not detail return values. However, with 0% schema coverage on inputs and only two required parameters, the description should have documented the workspace/dataset parameters. Adequate but missing critical input documentation.

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

Parameters2/5

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

Schema description coverage is 0% (no descriptions for workspace_id or dataset_id), and the description fails to compensate by explaining these parameters. While it mentions operating 'in a Power BI dataset' providing loose context, it does not explicitly map to or define the required parameters.

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 provides a specific verb ('List') and resource ('visible tables in a Power BI dataset'), clearly defining the scope. It distinguishes itself from potential siblings by specifying it excludes hidden/internal tables and explicitly mentions it feeds into `list_measures` and `list_columns`.

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?

Provides explicit chaining guidance: 'Use the returned table names in `list_measures`, `list_columns`, and DAX queries', directly referencing sibling tools. Also implies scope limitations (excludes hidden tables), though it could more explicitly state when NOT to use it.

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

Deploy Server