Skip to main content
Glama
umangnine

OneNote MCP Server

by umangnine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_notes

Search all OneNote notebooks and sections for a text query, returning matching sections with snippets of the matched content.

Instructions

Search for text across ALL notebooks and sections.

Searches through the text content of every section for the given query.
Returns matching sections with a snippet of the matched text.

Args:
    query: The text to search for (case-insensitive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Discloses basic behavior (search all notebooks, returns snippets, case-insensitive) but lacks details on performance, limitations, or error conditions. Without annotations, the description carries full burden; it is adequate but not comprehensive.

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?

Extremely concise: two sentences plus a parameter description. Every word is necessary and front-loaded with the tool's purpose.

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?

With an output schema present, the description adequately covers return behavior ('matching sections with a snippet'). Could mention pagination or max results, but not essential for a one-parameter search.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It adds 'case-insensitive' detail beyond the schema property title 'Query', providing valuable usage context.

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

Purpose5/5

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

The description uses specific verb 'search' and resource 'text across ALL notebooks and sections', clearly distinguishing from sibling tools that list or read specific items.

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?

States what it does ('searches through text content of every section') but does not explicitly mention when to avoid or suggest alternatives, though no obvious alternatives exist among siblings.

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