Skip to main content
Glama

Create OneNote Notebook

create_onenote_notebook

Creates a new OneNote notebook with the specified display name, enabling users to organize and store notes in Microsoft 365.

Instructions

Create a new OneNote notebook

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": {
      "display_name": "<display_name>"
    },
    "name": "create_onenote_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
display_nameYesNotebook name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safe-profile question is answered structurally. The description adds no behavioral context beyond that: it does not say whether the notebook is created in the user's default location, whether it requires a section to be created first, or what is returned on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one short, front-loaded sentence with no wasted clauses, but the brevity comes at the cost of content rather than from efficiency. The sentence is effectively a duplicate of the tool title.

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?

For a mutation tool with no output schema and no annotations describing side effects, the definition leaves out what an agent needs: where the notebook lands, whether the call is idempotent for duplicate names, and what the response contains. Its simplicity limits the damage, but it is still under-specified.

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% for the single required parameter display_name, so the schema already documents the input fully. The description adds no meaning about notebook naming constraints, uniqueness, or scope, which is the baseline-3 case when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Create a new OneNote notebook'), so the action is intelligible, but it is essentially a restatement of the title with no scope detail. Nothing distinguishes it from siblings such as create_onenote_section or create_onenote_page beyond the noun 'notebook'.

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?

There is no guidance on when to use this tool versus the related create_onenote_page or create_onenote_section tools, and no stated prerequisites. The agent must infer that a notebook must exist before sections or pages can be created.

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