Skip to main content
Glama

Data Montreal

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.6/5.0
Behavior4/5

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

Annotations provide idempotent and non-destructive hints. Description adds scoping, retention policy, and user-based persistence, complementing annotations well. Could mention overwrite behavior.

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?

Compact description covering purpose, usage, pairing, and persistence. Slightly dense but earns its sentences.

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?

For a simple 2-param tool with no output schema, the description covers all essential aspects: what it stores, scope, retention, and pairing with related tools.

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% with clear descriptions. Description adds valuable examples of key/value usage, enhancing semantic understanding beyond 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?

Clearly states the tool saves data for reuse later with concrete examples (ticker, address, preference, subject). Distinguishes from siblings recall and forget.

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?

Explicitly says when to use ('when you discover something worth carrying forward') and mentions alternatives (recall, forget). Also explains persistence details.

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

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

A4/5.0
Disambiguation3/5

Most tools have distinct purposes with detailed descriptions, but ask_pipeworx_beta is explicitly identical to ask_pipeworx, and the several polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage) have overlapping prediction-market territory. Descriptions help differentiate, but the overlaps could still cause misselection.

Naming Consistency4/5

The majority follow a clear verb_noun snake_case pattern (e.g., compare_entities, resolve_entity, generate_llms_txt). A few tools deviate with noun/adjective prefixes (montreal_datasets, montreal_recent, pipeworx_feedback, recent_alerts) or single verbs (remember, recall, forget), but the overall style is consistent and readable.

Tool Count2/5

At 34 tools, the set exceeds the 25+ threshold and feels heavy. While each tool has a distinct role, the sheer number—spanning data access, prediction markets, memory, subscriptions, and meta-tools—makes the surface harder for agents to navigate compared to a more focused server.

Completeness4/5

For its broad data-gateway purpose, the server covers a wide range: lookups, research, entity resolution, claim validation, memory, subscriptions, and feedback. The Montreal-specific subset (datasets, query, recent) is adequate for the apparent scope, with only minor gaps like no subscription-update tool.

Resources