Skip to main content
Glama

Montreal Events

by io.github.pipeworx-io

Compare Entities

compare_entities
Read-onlyIdempotent

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only and idempotent behavior; description adds parallel execution, off-calendar fiscal year handling, FAERS source for drugs, sorting by primary metric, and citation URIs—significant added context.

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?

Description is front-loaded with trigger phrases and covers all necessary aspects without fluff. Slightly lengthy but each sentence adds value; could be marginally tighter.

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?

Covers inputs, behavior, and output (paired data + citation URIs). No output schema exists, but description implies structured results. Adequate for the complexity.

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%, but description enriches by explaining the value format (tickers/CIKs for company, drug names for drug) and the max items constraint, adding clarity beyond 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 lists natural language triggers ('Compare X and Y', 'X vs Y'), specifies the action as side-by-side comparison of 2-5 entities, and distinguishes from siblings by noting it replaces multiple sequential lookups.

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?

Explicitly states to prefer this over sequential lookups when comparing entities, and details the two type options and their data sources. Lacks explicit 'when not to use' but context is clear enough.

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