Skip to main content
Glama
snahrup

Microsoft Fabric MCP Server

by snahrup

create_notebook

Create a new notebook in Microsoft Fabric workspace to organize code, data analysis, and documentation for collaborative projects.

Instructions

Create a new notebook in Fabric workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesThe workspace ID
nameYesName of the notebook
contentYesNotebook content/definition

Implementation Reference

  • Handler in the MCP server that parses the arguments for 'create_notebook' and calls the fabricClient.
    case 'create_notebook': {
      const { workspaceId, name, content } = CreateNotebookSchema.parse(args);
      const notebook = await fabricClient.createNotebook(workspaceId, name, content);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(notebook, null, 2),
          },
        ],
      };
    }
  • Zod schema definition for validating the 'create_notebook' tool input.
    const CreateNotebookSchema = z.object({
      workspaceId: z.string().describe('The workspace ID'),
      name: z.string().describe('Name of the notebook'),
      content: z.any().describe('Notebook content/definition'),
    });
  • The underlying API call implementation for creating a notebook in Microsoft Fabric.
    async createNotebook(workspaceId: string, name: string, content: any): Promise<FabricNotebook> {
      try {
        const response = await this.apiClient.post(`/workspaces/${workspaceId}/notebooks`, {
          displayName: name,
          definition: content
        });
        return response.data;
      } catch (error) {
        console.error('Error creating notebook:', error);
        throw error;
      }
    }
  • src/index.ts:105-124 (registration)
    Registration of the 'create_notebook' tool in the listTools response.
    name: 'create_notebook',
    description: 'Create a new notebook in Fabric workspace',
    inputSchema: {
      type: 'object',
      properties: {
        workspaceId: {
          type: 'string',
          description: 'The workspace ID',
        },
        name: {
          type: 'string',
          description: 'Name of the notebook',
        },
        content: {
          type: 'object',
          description: 'Notebook content/definition',
        },
      },
      required: ['workspaceId', 'name', 'content'],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't disclose important behavioral traits: whether this requires specific permissions, what happens on failure, whether notebooks can be overwritten, or any rate limits. For a creation tool with zero annotation coverage, this leaves significant gaps.

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, efficient sentence that states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information. Every word earns its place, making it easy for an agent to parse quickly.

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?

Given this is a creation/mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (e.g., returns notebook ID, success/failure indicators), doesn't mention error conditions, and provides minimal behavioral context. For a tool that creates resources, more information about the operation's behavior and outcomes would be helpful.

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?

The schema description coverage is 100%, with all three parameters clearly documented in the schema itself. The description adds no additional parameter semantics beyond what the schema already provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 clearly states the action ('Create') and resource ('new notebook in Fabric workspace'), making the purpose immediately understandable. It doesn't differentiate from sibling tools, but since none of the listed siblings appear to be notebook creation tools, this isn't a significant gap. The description avoids tautology by specifying what's being created and where.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing workspace access), when not to use it, or what alternatives might exist for similar functionality. The agent must infer usage context solely from the tool name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/snahrup/microsoft-fabric-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server