Skip to main content
Glama

Montreal Events

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).

TDQS

B3.3/5.0
Behavior1/5

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

The description discloses that setting mark_read:true flags events as read, which modifies server state. This directly contradicts the annotation readOnlyHint=true, which asserts no state modification. Per the scoring rules, this contradiction results in 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 at 3-4 sentences, front-loads the purpose, and every sentence provides useful information. No unnecessary words.

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

Completeness3/5

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

Covers returned fields, filtering, and polling, but omits explanation of pagination (limit) and unread_only behavior. Given the 5 optional parameters and no output schema, the description is moderately complete but has gaps.

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%, so the baseline is 3. The description adds context for type, since, and mark_read parameters, but does not cover limit or unread_only beyond what the schema already provides. This adds marginal value.

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

Purpose4/5

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

The description clearly states it pulls fired events from the subscription feed and lists the data fields returned. However, it does not differentiate itself from sibling tools like 'events', leaving the agent to infer which to use for subscribed alerts vs. general events.

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?

Provides guidance on filtering by type and since, and explains mark_read behavior for polling. Mentions an alternative REST endpoint for scripts/dashboards. Does not explicitly state when not to use this tool or compare to siblings like 'subscribe' or 'list_subscriptions'.

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

All Montreal Events 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

B3.4/5.0
Disambiguation2/5

The set contains multiple near-duplicate meta-query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools) and five overlapping Polymarket analysis tools, creating genuine selection ambiguity despite detailed descriptions. The single events tool is distinct, but it is drowned out by a crowd of similar data-research utilities.

Naming Consistency4/5

Almost all tools follow a consistent lowercase snake_case verb_noun pattern (ask_pipeworx, compare_entities, validate_claim, remember, forget). Only 'events' deviates by being a bare noun, but the overall convention is predictable and readable.

Tool Count1/5

32 tools is extreme for a server named 'Montreal Events', and only one tool actually relates to that domain. The remaining 31 form a sprawling, unrelated data-research, prediction-market, and memory toolkit that would overwhelm any agent trying to work with Montréal event data.

Completeness1/5

For the server's stated purpose, the surface is severely incomplete: a single read-only event search with no event details, venue info, categories, or management operations. The Pipeworx tools may cover their own domain thoroughly, but they contribute nothing to the Montreal Events scope.

Resources