Skip to main content
Glama

Montreal Events

by io.github.pipeworx-io

Events

events
Read-onlyIdempotent

Find upcoming public events in Montréal, Canada. Filter by keyword, borough (arrondissement, e.g. "Ville-Marie", "Le Plateau-Mont-Royal") and date window. Returns events sorted by start date. Content is in French.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclude events starting on/before this date YYYY-MM-DD.
fromNoInclude events ending on/after this date YYYY-MM-DD (default: today).
limitNoMax events (1-50, default 20).
queryNoKeyword over title and description, e.g. "musique", "festival", "famille".
offsetNoPagination offset (default 0).
boroughNoFilter by arrondissement, e.g. "Ville-Marie", "Le Plateau-Mont-Royal", "Rosemont".

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that content is in French and events are sorted by start date, providing useful behavioral context beyond annotations.

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?

Two sentences, front-loaded with purpose, and no wasted words. Efficient and clear.

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?

For a read-only query tool with full schema coverage and no output schema, the description is sufficiently complete. It explains sorting and language, but does not mention pagination (offset) which is in the schema.

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 description coverage is 100%, so baseline is 3. The description mentions filtering by keyword, borough, and date window but does not add meaning beyond what the schema provides. The example boroughs are also in the schema.

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 finds upcoming public events in Montréal with filtering options. It uses a specific verb ('Find') and resource ('upcoming public events'), and the scope ('Montréal, Canada') distinguishes it from siblings that are unrelated.

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

Usage Guidelines3/5

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

The description implies usage for Montréal events but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. No guidance on when not to use it is given.

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