Skip to main content
Glama

Résidences Montréal

Get one residence's record

get_residence
Read-onlyIdempotent

Full record of one Montréal private seniors' residence from Québec's official register: category, operator, units, services (meals, help, personal assistance, nursing, memory care), building features (elevators, sprinklers, generator, air conditioning), phone and links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "residence": "<residence>"
    },
    "name": "get_residence"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer: 'fr' or 'en'.en
residenceYesThe residence's register number (from search results) or its name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real context beyond that — the data comes from Québec's official register and the record spans services and building features — but says nothing about behavior when a residence name is ambiguous or not found.

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?

A single front-loaded sentence identifying the resource and source first, then enumerating contents. The parenthetical field lists are dense but each item tells the agent what to expect in the record, so little is wasted.

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?

With a full output schema and complete annotations, the description only needs to set scope and provenance, which it does (one residence, official register, field domains). Only the ambiguous-name / not-found behavior is left uncovered.

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%; both the residence identifier and the fr/en language enum are documented in the schema, including that the register number comes from search results. The description adds no parameter meaning beyond that, so 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+resource: 'Full record of one Montréal private seniors' residence.' The singular 'one' plus the field inventory (category, operator, units, services, building features, phone, links) makes it clearly distinct from search_residences (plural listing) and compare_residences without opening either schema.

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?

Usage is only implied: an agent can infer this is the detail-fetch step after a search, but the description never says when to call this versus search_residences or compare_residences, and names no prerequisites or exclusions.

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