Skip to main content
Glama

Microsoft Onenote

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description indicates that setting mark_read:true flags events as read, modifying server state. This directly contradicts the annotations, which declare readOnlyHint=true. According to scoring rules, a contradiction earns a score of 1.

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?

The description is concise—four sentences—with the purpose front-loaded. Every sentence adds meaningful information without redundancy. Structure efficiently groups purpose, return fields, filter options, and usage note.

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?

Given the 5 optional parameters and no output schema, the description adequately covers return fields and key behaviors like mark_read. It mentions an alternative endpoint for scripting. Missing details include pagination behavior beyond limit, error handling, and authentication requirements, but overall is reasonably complete.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the type filter with an example ('sec_8k'), clarifying since is an ISO timestamp, and detailing mark_read and unread_only behavior. This goes beyond the schema's minimal descriptions.

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 clearly states the tool pulls fired events from subscription feeds and specifies what each returned event carries (source, citation_uri, payload). It distinguishes itself from siblings like list_subscriptions by focusing on events rather than subscriptions, and mentions an alternative endpoint for scripts/dashboards.

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?

The description explains when to filter by type and since, and how mark_read affects subsequent calls. It notes that polling works fine. However, it does not explicitly exclude alternative tools or state when not to use this tool compared to siblings like validate_claim or search_within.

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

All Microsoft Onenote toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools are genuinely easy to confuse: ask_pipeworx and ask_pipeworx_beta are explicitly described as currently identical, and the five polymarket_* tools overlap significantly in purpose. There are also wrapper-like pairs such as ai_visibility_check vs. scan_competitor_ai_presence and entity_profile vs. recent_changes vs. compare_entities that require reading long descriptions to disambiguate.

Naming Consistency3/5

The names are mostly lowercase snake_case and readable, but there is no consistent verb_noun pattern: entity_profile and recent_changes are noun phrases, pipeworx_trending and pipeworx_feedback use a prefix, ask_pipeworx_beta is a single-family variant, and scan_competitor_ai_presence uses a different structure from ai_visibility_check. The naming is not chaotic, but it is a mix of conventions.

Tool Count1/5

A server labeled Microsoft Onenote exposes 31 tools, none of which actually relate to OneNote note-taking, notebooks, or pages. Even as a general research/prediction-market server, 31 tools is far above the coherent range, and for the stated product purpose this count is wildly inappropriate.

Completeness1/5

For the server's declared OneNote domain, there is zero coverage: no tools for creating, reading, updating, or deleting notes, pages, sections, or notebooks. The actual tool surface is centered on Pipeworx data lookups, Polymarket arbitrage, and memory helpers, which leaves the apparent note-taking domain completely unrepresented.

Resources