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

mcp-fabric-api

by mkoziel2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notebook_list

Read-only

List all notebooks in a Microsoft Fabric workspace by providing its workspace ID. Retrieve the complete inventory of notebooks for analysis or management.

Instructions

List all notebooks in a workspace

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A4/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, so the safety profile is covered. The description adds the workspace-scoped listing behavior but says nothing about pagination, ordering, or return format, though these are not essential for a simple read-only list.

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, front-loaded sentence with no filler. Every word is informative and the description is not bloated.

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 one-parameter, read-only list operation with annotations covering safety, the description is largely complete. It could mention pagination or return fields, but the lack of an output schema and the simplicity of the tool make these omissions acceptable.

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 is already documented. The description reinforces that the parameter selects the workspace, but adds no extra semantics beyond the schema.

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 uses a specific verb ('List'), a clear resource ('notebooks'), and an explicit scope ('in a workspace'), which distinguishes it from sibling tools like notebook_get (single notebook) and other resource listers. It states exactly what the tool does.

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?

The description makes the intended use obvious: retrieve all notebooks within a given workspace. It does not explicitly name alternatives or state when not to use it, but the scope and resource naming provide clear context without ambiguity.

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