Skip to main content
Glama

Outlook Contacts

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.5/5.0
Behavior1/5

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

The description claims mark_read:true flags events as read, implying a side-effect, which contradicts the annotation readOnlyHint=true. This is a serious inconsistency that misleads about the tool's safety profile.

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 concise with four sentences, front-loading the main purpose. It could be more structured but contains no wasted words.

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 no output schema, the description provides return field details, filtering, mark_read behavior, and alternative access. It lacks explanation of pagination and ordering, but is fairly complete for the tool's complexity.

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 coverage is 100%, but the description adds context only for type, since, and mark_read. It does not explain limit or unread_only beyond the schema, so the added value is partial.

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 the subscription feed, specifies the return fields (source, citation_uri, raw payload), and distinguishes it from sibling tools by focusing on recent alerts retrieval.

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 mentions that polls work fine and provides an alternative access method (GET endpoint), giving clear usage context. However, it does not explicitly compare with sibling tools or state when not to use.

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