Skip to main content
Glama

Résidences Montréal

Search Montréal seniors' residences

search_residences
Read-onlyIdempotent

Find private seniors' residences (RPA) on the island of Montréal from Québec's official register, filtered by place, needs, category or name. Returns each residence's address, phone, category, key services, register record and, when there is one, a guide page on residences-montreal.com.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_residences"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoNeighbourhood, borough or city on the island of Montréal, or a postal code start (e.g. 'Ahuntsic', 'Rosemont', 'Pointe-Claire', 'H2M'). Leave empty for the whole island.
nameNoPart of the residence's name.
limitNoMaximum number of residences to return.
needsNoServices or features the residence must have, as declared in the register: nursing_care (nurses on staff); personal_assistance (help with hygiene, dressing, bathing...); medication_administration (staff give medication); accepts_wandering_risk (the residence says it takes residents who wander or may leave unnoticed; relevant for dementia, but not proof of a specialised memory-care unit); exit_alarm (alarm when a resident leaves); meals; housekeeping; elevator; air_conditioning_in_units; full_sprinklers; generator; non_profit (operator).
languageNoLanguage of the answer: 'fr' or 'en'.en
categoriesNoRPA categories to include (1-2: independent seniors; 3: semi-independent; 4: moderate to severe loss of autonomy).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by naming the data provenance (Québec's official register) and disclosing the shape of the return payload, including that guide pages exist only for some residences. It stops short of saying how truncation by limit behaves.

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 the verb, resource, and scope before the filter and return details. No filler or repetition.

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?

The tool is a moderately complex multi-filter search, and the description plus a fully-covered schema and an output schema make it callable with confidence. Minor redundancy in enumerating return fields that the output schema already defines, and no statement about result truncation or empty-result handling.

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?

With 100% schema description coverage, the schema already documents area, name, needs, categories, language and limit in detail, including enum semantics for the needs list. The description only restates the filter axes ('place, needs, category or name') and omits limit and language, so the baseline 3 applies.

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?

States a specific verb and resource ('Find private seniors' residences (RPA)'), the geographic scope (island of Montréal), the data authority (Québec's official register) and the filter dimensions. An agent can immediately tell this is a filtered discovery search rather than a single-record lookup.

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 via 'filtered by place, needs, category or name' and the schema notes 'Leave empty for the whole island', which signals a browse-all mode. However, it never states when to prefer this over siblings like get_residence, compare_residences or list_areas, nor any exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources