Skip to main content
Glama

onenote_read

Read-only

Reads a single OneNote page as plain text by page ID, enabling retrieval of notebook page content for review or processing.

Instructions

Read one OneNote page as text.

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": "onenote_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one genuinely useful behavioral fact — content is returned as text rather than raw HTML or structure — but says nothing about truncation, page size limits, auth requirements, or what happens when the page is missing.

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?

A single seven-word sentence with the verb and resource front-loaded and zero filler. Nothing could be removed without losing meaning.

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?

This is a simple single-parameter read tool and an output schema exists, so return values need no explanation. The one remaining gap is that the description never explains how to obtain a valid page_id, which matters because the schema offers no help there.

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 single page_id parameter has 0% schema description coverage, so the schema contributes nothing about its format or provenance. The description only implies that the id selects one page; it does not say where to obtain it (e.g., from onenote_pages) or whether it is an opaque GUID.

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?

"Read one OneNote page as text" names a specific verb (read), a specific resource (a single OneNote page), and the output form (text). The word "one" implicitly contrasts with the sibling list-style tools onenote_pages and onenote_notebooks, though it never names an alternative explicitly.

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 explicit when-to-use guidance, no statement that page_id must come from onenote_pages, and no note about what happens with a notebook or section id. Usage is only inferable from the verb and the singular resource.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.