Skip to main content
Glama
Sign In
onenote_mcp_server

onenote_mcp_server

by ItsikBin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_section

Create a new section in an existing OneNote notebook by providing the notebook ID and a display name.

Instructions

Create a new section in a OneNote notebook for the configured account.

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

Input Schema

NameRequiredDescriptionDefault
notebook_idYesThe ID of the OneNote notebook
display_nameYesName for the new section (max 128 characters, no special chars ? * \ / : < > | ' ")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral transparency. It does not disclose side effects, permission requirements, error conditions, or whether duplicate names are allowed, leaving the agent without important context.

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 concise sentence that front-loads the action and resource, with no unnecessary words.

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

Completeness3/5

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

For a simple create operation with two documented parameters, the description is adequate but lacks context about prerequisites (e.g., notebook existence) and potential error responses. No output schema exists, so return values are not covered, but the description still leaves gaps.

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 input schema fully documents both notebook_id and display_name with descriptions, so the description adds no extra semantic value. Baseline of 3 is appropriate.

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 the specific verb 'Create' and resource 'section in a OneNote notebook', clearly distinguishing it from sibling tools like list_sections and create_page.

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 is provided on when to use this tool versus alternatives, such as when a notebook must be created first or how it differs from create_page. The description only states what it does without contextual usage.

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