Skip to main content
Glama

Outlook Contacts

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

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) already indicate safety. The description adds rich behavioral details: fan-out to multiple APIs, fallback from GDELT to GNews, soft-fail for USPTO due to sunset, and the return structure (changes[], total_changes, citation URIs). No contradictions.

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

Conciseness4/5

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

The description is a single dense paragraph. It is front-loaded with example queries but could be more scannable with breaking into sentences or bullet points. However, every sentence adds value—no fluff. It earns a 4 for being effective but slightly unstructured.

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 3 parameters, full schema coverage, and rich annotations, the description covers the return format (changes[], total_changes, URIs), source details, fallback mechanisms, and when to use the sibling tool. No output schema exists, so the description compensates well by outlining the return structure. The agent has all necessary context to invoke correctly.

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 100%, so descriptions for all three parameters are present. The description expands on the 'since' parameter with examples ('2026-04-01', '7d', '30d', '3m', '1y') and a recommended default ('30d' or '1m'). For 'value', it clarifies ticker or CIK format. The 'type' parameter is noted as only 'company' supported. While helpful, the description doesn't detail how each parameter affects the fan-out logic, leaving room for improvement.

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 starts with user-facing example queries ('What's new with X') and clearly states it's a 'change feed for a company in the last N days/weeks/months in ONE parallel call.' It identifies the verb as 'recent changes' and distinguishes from the sibling 'entity_profile' by contrasting dynamic vs. static profile. The purpose is specific and unambiguous.

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?

The description explicitly tells when to use the tool ('change feed...') and when to use the alternative ('Use entity_profile instead when you want the static profile...'). It also outlines the data sources (SEC EDGAR, GDELT→GNews, USPTO) and fallback behavior, providing situational guidance.

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

All Outlook Contacts 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.6/5.0
Disambiguation2/5

Several tools are near-duplicates by name and function, notably ask_pipeworx vs ask_pipeworx_beta, and the dense Polymarket family (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). Long descriptions help, but an agent cannot reliably pick between these without reading closely.

Naming Consistency4/5

Almost all names are lowercase_snake_case and mostly verb-leading (discover_tools, resolve_entity, unsubscribe), but there are noun-first exceptions (entity_profile, recent_changes, pipework_trending) and several phrasal or compound forms. This is a minor deviation from a clean verb_noun pattern rather than a chaotic mix.

Tool Count2/5

31 tools is over the heavy threshold, and the set feels bloated: multiple query routers, a half-dozen overlapping Polymarket tools, and two AI-visibility probes that could be merged. The count is especially hard to justify for a server named Tools 'OutLook Contacts', since none are contact management.

Completeness1/5

For the server's stated domain, Outlook Contacts, there are zero tools in that domain — no create contact, no list contacts, no update, no delete, no folders or mailboxes. Even though the actual Pipework toolkit is broad for its own domain, this set fails its declared intend domain entirely.

Resources