mcp-fabric-api

semantic_model_take_over

Take over ownership of a Power BI semantic model by providing workspace and model IDs, enabling full control for management and troubleshooting.

Instructions

Take over ownership of a semantic model via the Power BI API

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": {
      "workspaceId": "<workspaceId>",
      "semanticModelId": "<semanticModelId>"
    },
    "name": "semantic_model_take_over"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID (Power BI group ID)
`semanticModelId`	Yes	The semantic model/dataset ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description discloses that ownership changes but provides no behavioral detail about consequences, such as whether the previous owner loses access, whether permissions are altered, or whether the operation is reversible. Annotations only state non-read-only and non-destructive, which do not convey the full impact of a takeover.

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, straightforward sentence with no wasted words. 'Via the Power BI API' is slightly redundant given the context, but overall it is concise and front-loaded.

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

Completeness2/5

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

For a potentially impactful operation like taking over ownership, the description lacks essential context such as prerequisites, side effects, permission requirements, or behavior after execution. The simple schema and lack of output schema make the description the only source of behavioral guidance, and it is insufficient.

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?

Both parameters are fully documented in the input schema with clear descriptions (workspaceId and semanticModelId). The tool description adds no additional parameter semantics, but since schema coverage is 100%, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('take over ownership') and a clear resource ('semantic model'), which differentiates it from siblings like semantic_model_update_details or semantic_model_delete. However, it does not explain what 'take over' entails operationally, leaving some ambiguity for an agent unfamiliar with the Power BI ownership model.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when this tool should be used, what prerequisites exist, or when an alternative such as semantic_model_update_details would be more appropriate. The description simply states the action with no context for selection.

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

Deploy Server