Skip to main content
Glama
Sign In
onenote_mcp_server

onenote_mcp_server

by ItsikBin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_page

Create a new page in a OneNote section using HTML content. Add a titled page to any section with optional HTML body; script tags are stripped for security.

Instructions

Create a new page in a OneNote section. The content should be HTML. Script tags and event handlers are stripped for security.

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": {
      "section_id": "<section_id>",
      "title": "<title>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPage title (max 128 characters)
section_idYesThe ID of the OneNote section
html_contentNoHTML content for the page body (e.g. <h1>Heading</h1><p>Content</p>). Defaults to a blank page if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the transparency burden. It discloses a key behavioral trait: script tags and event handlers are stripped for security. However, it doesn't mention permissions, side effects, or return value, leaving some 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?

Two sentences, front-loaded with the action, and every word earns its place. No filler or repetition of schema details.

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 create tool with 3 parameters and no output schema, the description covers purpose, parameter expectations, and a security note. It's slightly incomplete regarding usage guidance relative to siblings and return behavior, but adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are already described in the schema (100% coverage), but the description adds value by clarifying that html_content should be HTML and that security filtering applies. This enriches the parameter 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 states a specific action ('Create a new page') and resource ('OneNote section'), clearly distinguishing it from siblings like create_section and update_page. The verb and object are unambiguous.

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 context of when to use the tool is clear: when a new page needs to be created in an existing OneNote section. It doesn't explicitly mention alternatives or exclusions, but the sibling list itself makes the distinction apparent.

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