Skip to main content
Glama
Sign In
mcp-fabric-api

mcp-fabric-api

by mkoziel2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lakehouse_list_shortcuts

Read-only

Retrieve all OneLake shortcuts in a lakehouse by supplying workspace and lakehouse IDs. Get a complete list of shortcuts to manage data connections.

Instructions

List all OneLake shortcuts in a lakehouse

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

Input Schema

NameRequiredDescriptionDefault
lakehouseIdYesThe lakehouse ID
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the operation lists 'all' shortcuts, indicating an unfiltered scope, but does not disclose return format, pagination, or potential performance traits. No contradiction with annotations.

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?

The description is a single seven-word sentence: 'List all OneLake shortcuts in a lakehouse.' It is front-loaded with the verb, concise, and every word contributes to meaning.

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?

For a simple, read-only, two-parameter list operation, the description provides enough context for selection and invocation. It does not describe return fields or pagination, but absent an output schema and given the straightforward nature of a list-all tool, this is a minor gap rather than a critical omission.

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%: both workspaceId and lakehouseId have descriptions already. The description only reinforces that the listing occurs within a lakehouse, adding no new parameter-level meaning.

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 states a specific verb ('List'), a specific resource ('OneLake shortcuts'), and a scope ('in a lakehouse'). It clearly distinguishes itself from siblings like lakehouse_list_tables (tables) and lakehouse_get_shortcut (a single shortcut).

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 verb and resource imply usage: an agent should select this tool when it needs to enumerate shortcuts in a lakehouse. However, it does not explicitly mention alternatives or when not to use it, leaving some inference required despite the suggestive sibling names.

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

Deploy Server

Other Tools