Skip to main content
Glama

Résidences Montréal

Compare residences

compare_residences
Read-onlyIdempotent

Compare 2 to 4 Montréal seniors' residences side by side from the official register: category, operator, size, services, building features 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": {
      "residences": "<residences>"
    },
    "name": "compare_residences"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer: 'fr' or 'en'.en
residencesYes2 to 4 register numbers or names.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds genuine context beyond that — the authoritative source ('official register') and the compared field set — but says nothing about lookup failures when a register number/name is ambiguous or unmatched, which matters for a batch keyed on free-text names.

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?

A single sentence with the verb and scope front-loaded, followed by the compared fields. Nothing is redundant and nothing needs re-reading.

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 an output schema present, return values need no explanation, and annotations cover safety; the description supplies the missing pieces an agent needs — source authority, cardinality, and comparison dimensions. Only the name-vs-register-number ambiguity handling is left unstated.

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%, including an enum and default for language and min/max bounds on residences, so the baseline is 3. The description reinforces the 2-to-4 cardinality but does not clarify whether names or register numbers are preferred or how ambiguity is resolved, and the language parameter is not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compare) and resource (Montréal seniors' residences) with hard scope bounds (2 to 4) and an explicit data source ('official register'), then enumerates the compared dimensions. It stops short of naming which sibling it displaces (e.g. get_residence for a single lookup), so differentiation is inferred rather than stated.

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 '2 to 4 ... side by side' framing implies the situation it serves (multi-residence comparison), but there is no explicit when-to-use/when-not guidance and no mention of search_residences or get_residence as alternatives for other lookup shapes. Usage is left to inference from the cardinality constraint.

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