Skip to main content
Glama

Read OneNote Page

get_onenote_page_content
Read-only

Retrieves the HTML content of a OneNote page by page ID, so an AI assistant can read, summarize, or process the page's notes.

Instructions

Get OneNote page content as HTML

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": {
      "page_id": "<page_id>"
    },
    "name": "get_onenote_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description's main added value is disclosing that the payload comes back as HTML rather than plain text or structured objects. It says nothing about behavior for large pages, truncation, or how embedded images/attachments are represented, which are real concerns for page-content retrieval.

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

Conciseness4/5

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

A single short sentence with the return format front-loaded and no wasted wording. It is arguably terse to the point of under-specification, but nothing in it is redundant.

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 one-parameter read tool with a readOnlyHint and no output schema, the description covers what is returned (HTML) but omits how to source the page_id and any caveats about content size or structure. Adequate but with clear gaps an agent would likely hit in practice.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents page_id. The description adds no format hints (e.g., whether the ID comes from a list call or a URL) beyond what the schema provides, which is the expected baseline for this coverage level.

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 names a specific verb ('Get') and resource ('OneNote page content') and adds the return format ('as HTML'), so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings such as list_onenote_pages or read_document, though the resource name makes the domain fairly obvious.

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 when-to-use guidance, no mention of how to obtain a page_id (e.g., via list_onenote_pages), and no statement of when a different tool would be preferable. Usage is only implied by the verb.

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