Microsoft Fabric MCP Server

fabric_get_shortcut

Read-only

Fetch a specific OneLake shortcut by specifying the hosting item, its parent path, and the shortcut name.

Instructions

Get a single OneLake shortcut by path + name.

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": {
      "itemId": "<itemId>",
      "shortcutPath": "<shortcutPath>",
      "name": "<name>"
    },
    "name": "fabric_get_shortcut"
  }
}

Input Schema

Name	Required	Description
`itemId`	Yes	Item ID that hosts the shortcut (e.g. a lakehouse)
`shortcutPath`	Yes	Shortcut parent path, e.g. "Files" or "Tables"
`name`	Yes	Shortcut name
`workspace`	No	Workspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, so the description doesn't need to restate read-only nature. Description adds the 'by path + name' detail, but that is already in parameter schemas. No additional behavioral context like return shape or error handling.

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?

Single sentence, zero wasted words. Front-loaded with purpose. Appropriate for a simple get operation.

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

Completeness4/5

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

Tool is low complexity, schema covers all params, and no output schema exists. Description could mention that it returns the shortcut details, but not required. Still adequate for an agent to understand the tool's function.

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 coverage is 100% with descriptions for all parameters. The description adds no new meaning beyond what the schema already provides, so baseline score of 3.

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 'Get a single OneLake shortcut by path + name': specific verb, resource, and method. Distinguishes from sibling tools like fabric_list_shortcuts and fabric_create_shortcut.

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 on when to use this tool versus alternatives like list or create. No prerequisites or context provided. The description only states what it does, not when to deploy it.

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

Deploy Server