Skip to main content
Glama
Sign In
onenote-mcp-python

onenote-mcp-python

by eddyficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

onenote_navigate

Opens a specific notebook, section, or page in OneNote's visible window to display the requested item on screen.

Instructions

Open a notebook, section, or page in the visible OneNote window. This changes what the user sees on screen — use only when the user asked to open or show something.

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": {
      "object_id": "<object_id>"
    },
    "name": "onenote_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesObject ID to navigate to. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses that the tool changes what the user sees on screen, which is a behavioral side effect beyond the annotations' readOnlyHint: false. This clarifies the nature of the mutation (UI navigation rather than data modification).

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 two sentences, with the primary action in the first sentence and usage constraints in the second. No wasted words.

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

Completeness5/5

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

The tool is simple, and the description covers the action, the target object types, the side effect, and the usage condition. No output schema is needed.

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?

The only parameter is object_id, and the description clarifies that it refers to a notebook, section, or page ID, adding meaning to the schema. Since schema coverage is 100%, this is a bonus.

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 clearly states the tool opens notebooks, sections, or pages in the visible OneNote window, using the verb 'open' and listing the resource types. This distinguishes it from sibling tools that create, delete, or modify content.

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?

It explicitly states when to use it: 'use only when the user asked to open or show something.' This provides clear usage guidance, though it does not name alternative tools explicitly.

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