MCP Server for Power BI

get_workspace_id

Retrieve the workspace ID for a Power BI workspace by providing its display name, required for subsequent operations like listing datasets.

Instructions

Get the workspace ID for a given workspace name.

This tool is useful for finding the workspace ID when you only know the workspace name. The ID is required for other operations like listing datasets.

Args: workspace_name: The display name of the Power BI workspace.

Returns: The workspace ID as a string.

Raises: ToolError: If the workspace is not found.

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_name": "<workspace_name>"
    },
    "name": "get_workspace_id"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, but description discloses that the tool raises a ToolError if not found. It's a simple get operation with no destructive side effects; description sufficiently covers behavior.

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?

Description is concise with a brief summary and structured Args/Returns/Raises sections. No wasted sentences, front-loaded with purpose.

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?

For a simple 1-param tool with output schema, description covers purpose, parameter semantics, return value, and error case. No missing information.

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?

Input schema has no description for parameter workspace_name (0% coverage). Description provides meaning: 'The display name of the Power BI workspace.' Fully compensates for schema gap.

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?

Description clearly states it gets the workspace ID for a given workspace name. Distinguishes from sibling tools like powerbi_list_workspaces which likely list all workspaces, whereas this is a lookup by name.

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?

Explicitly says when to use: when only the workspace name is known, and explains that the ID is needed for other operations. Does not explicitly mention when not to use, but context is clear.

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

Deploy Server