Skip to main content
Glama

onenote_pages

Read-only

List OneNote pages newest first across all notebooks or within a specific section, and filter results by title.

Instructions

List OneNote pages, newest first: across all notebooks, or in one section (id from onenote_notebooks). title_contains filters by title.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onenote_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
section_idNo
title_containsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the safety profile is covered. The description usefully adds that results are ordered newest-first and that filtering is available, but says nothing about the result limit behaviour or how many pages a caller should expect, leaving the volume/pagination story unexplained.

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 tight sentences with the primary capability and ordering front-loaded, followed by the scoping caveat and filter note. Nothing is wasted or repeated from structured fields.

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?

An output schema exists, so return-value explanation is not required, and the description covers scope, ordering, and title filtering. The only meaningful gap is the undocumented limit parameter, which matters for a list tool that could return large result sets.

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 description coverage is 0%, so the description carries the burden. It explains section_id's provenance ('id from onenote_notebooks') and title_contains' filter effect, but the 'top' parameter (default 50) is never mentioned, leaving page-size/limit semantics undocumented.

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 and resource ('List OneNote pages') plus the ordering ('newest first') and the two scoping modes (all notebooks or one section). It does not explicitly distinguish itself from the sibling onenote_read, which likely fetches a single page, so an agent must infer that boundary.

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?

Clear guidance on the two usage modes and an explicit pointer that section_id comes from onenote_notebooks, which routes the agent to the prerequisite discovery call. No exclusion statements about when to prefer onenote_read or search over listing.

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