Skip to main content
Glama

List OneNote Sections

list_onenote_sections
Read-only

List sections in a OneNote notebook by notebook ID, with an option to fetch all pages of results. Use it to find and navigate sections before reading or managing pages.

Instructions

List sections in a OneNote notebook

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>"
    },
    "name": "list_onenote_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
notebook_idYesNotebook ID
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe, non-mutating read, so the description adds little. It does not mention pagination behavior despite the fetch_all_pages parameter, nor result ordering, truncation, or empty-notebook behavior.

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 front-loaded sentence with no redundant clauses. It is efficient, though the brevity borders on under-specification rather than tight editing.

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 two-parameter read-only tool with full schema coverage and a readOnlyHint annotation, this is minimally sufficient to call correctly. However, the pagination ceiling and the fact that results are scoped per notebook are left implicit, so it is adequate rather than complete.

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?

Schema coverage is 100%, so both notebook_id and fetch_all_pages are documented in the schema itself. The description only implies that sections are retrieved for a specific notebook, adding nothing about the 50-page cap or paging semantics beyond what the schema already says. Baseline 3 applies.

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?

States a specific verb (List) and resource (sections) and scopes it to 'in a OneNote notebook', which tells an agent the sections are notebook-bound rather than a flat listing. It does not explicitly distinguish itself from siblings like list_onenote_notebooks or list_onenote_pages, but the resource noun does most of that work.

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 guidance on when to use this versus list_onenote_pages or create_onenote_section, nor any stated prerequisite (e.g., that a valid notebook_id must be obtained from list_onenote_notebooks). The agent must infer the call context entirely.

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