Skip to main content
Glama

List OneNote Notebooks

list_onenote_notebooks
Read-only

Retrieve a user's OneNote notebooks to identify available notebooks and support selecting one for further note operations.

Instructions

List OneNote notebooks

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

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description contributes nothing beyond that: it does not mention pagination behavior, result ordering, default page size, or what happens when a user has no notebooks, all of which matter for a paged list tool whose only parameter is fetch_all_pages.

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

Conciseness3/5

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

The sentence is short with zero redundancy, but brevity here reflects under-specification rather than disciplined editing. There is nothing front-loaded beyond the bare resource name, and no structure to guide a reader.

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

Completeness2/5

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

For a simple list tool with no output schema, the description still needs to convey the result shape and pagination semantics, and it conveys neither. It also leaves the agent unable to distinguish this from sibling list tools without inspecting their schemas.

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 100% and there is a single optional parameter (fetch_all_pages) fully documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about pagination limits or when to set the flag, but it is not required to given the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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 prerequisites, and no pointer to alternatives for navigating OneNote hierarchy (sections, pages). An agent must infer that this is the top-level entry point into OneNote content purely from the resource name.

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