Skip to main content
Glama

Outlook Calendar

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

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

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Describes data sources, fallback behavior (GDELT→GNews), patent API sunset, and return structure (changes grouped by source, total_changes, citations). Adds value beyond annotations which already mark readOnly/idempotent.

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?

Single well-structured paragraph starts with examples, explains sources, parameter usage, return structure, and sibling distinction. Every sentence earns its place, no fluff.

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

Completeness5/5

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

Given complexity (multiple sources, fallback, parameter flexibility), description is complete. Covers data sources, since format, return type, and references sibling tool. No output schema but return structure is sufficiently described.

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

Parameters5/5

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

Schema has 100% coverage. Description adds examples for since (ISO date, relative shorthand), value (ticker or CIK), and type (only company). Provides extra 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?

Description clearly states it provides a change feed for a company (SEC filings, news, patents) with example queries. Distinguishes from sibling entity_profile by contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool ('what's new' queries over a window) and when to use entity_profile instead. Provides guidance on since parameter format.

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

All Outlook Calendar 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
Disambiguation1/5

The tool set spans at least four unrelated domains (calendar, memory, Pipeworx data lookup, Polymarket betting), and within the data-lookup domain ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions have heavily overlapping purposes. An agent cannot reliably tell which of the many query/betting tools to call.

Naming Consistency3/5

All names are snake_case, which is a plus, but the convention is inconsistent: verb_noun (list_events, remember), noun phrases (entity_profile, recent_changes), brand-prefixed families (pipeworx_*, polymarket_*), and irregular verbs (ask_pipeworx, generate_llms_txt, validate_claim). It is readable but not predictable.

Tool Count1/5

The server is named 'Outlook Calendar' but only 5 of 36 tools relate to calendars; the other 31 are unrelated memory, Pipeworx data, and prediction-market tools. This is an extreme scope mismatch—the tool count is wildly inappropriate for the server's stated purpose.

Completeness1/5

For an Outlook Calendar server, the surface is severely incomplete: it only supports reading (list_calendars, list_events, get_event, find_meeting_times, get_profile) with no create, update, delete, or invite-response operations. The unrelated domains are also incomplete as a coherent offering.

Resources