mcp-fabric-api

ml_model_create

Create a new ML model in a Microsoft Fabric workspace by providing a workspace ID, display name, and optional description. This long-running operation sets up the model for data engineering and analytics workflows.

Instructions

Create a new ML model in a workspace (long-running)

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

Input Schema

Name	Required	Description
`description`	No	Description of the ML model
`displayName`	Yes	Display name for the ML model
`workspaceId`	Yes	The workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutating nature is covered. The description adds the long-running behavior, which is a useful disclosure beyond annotations. However, it does not say what the operation returns, how to poll status, or whether creation can be retried on failure.

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?

A single sentence with no filler; the core action and distinguishing context are front-loaded. The long-running note is compact and informative. Nothing could be removed without losing value.

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?

The tool is a simple create with 3 fully documented parameters and no output schema, so the description only needs to cover operational behavior. The long-running warning is included, but the missing details about result retrieval or operation tracking leave an agent uncertain about next steps. Overall adequate but with clear gaps.

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 workspaceId, displayName, and description are all documented in the schema. The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 begins with a specific verb 'Create' and names the resource 'ML model' with scope 'in a workspace'. This clearly differentiates it from sibling tools like ml_model_update, ml_model_delete, and ml_model_list. The parenthetical 'long-running' adds a defining behavioral trait that aids selection.

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 gives some context (workspace scoping, long-running) but provides no explicit when-to-use guidance or exclusions. It does not mention alternatives, such as ml_model_update for modifying an existing model or ml_experiment_create for experiments. The intended usage is implied by the name rather than stated.

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

Deploy Server