Skip to main content
Glama

Résidences Montréal

Find guides on residences-montreal.com

find_guides
Read-onlyIdempotent

Search the practical guides on residences-montreal.com (choosing a residence, costs, moving, neighbourhoods, care levels) and return titles, summaries 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": {
      "query": "<query>"
    },
    "name": "find_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat the user wants to know, in a few words (e.g. 'moving a parent', 'memory care Rosemont', 'coût RPA').
languageNoLanguage of the guides: 'fr' or 'en'.en

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 readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds only that results include titles, summaries and links, which is largely duplicated by the existing output schema; nothing is said about result volume, ranking behavior, or empty-result handling.

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, front-loaded with the verb and resource, with the topic enumeration and return shape compactly appended. No filler or redundant restatement of the title.

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?

For a read-only search tool with an output schema and well-documented parameters, the description covers what is searched, which topics are in scope, and that results are guide links. It stops short of stating when an agent should prefer a sibling tool, which is the one remaining gap.

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?

With 67% schema description coverage, the schema already explains 'query' with examples and 'language' with an enum, and 'limit' carries a default and min/max bounds. The description adds nothing parameter-specific, but the topic list implicitly frames what queries are appropriate; baseline for this coverage level is 3, nudged up slightly by that framing.

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?

The description gives a specific verb ('Search') and resource ('practical guides on residences-montreal.com'), plus an enumerated topic scope (choosing a residence, costs, moving, neighbourhoods, care levels). It does not explicitly contrast itself with siblings such as costs_and_help, which share topical overlap, so the differentiation is partial rather than explicit.

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 implied by the topic list — an agent can infer this tool is for editorial/informational content rather than residence records — but there is no explicit statement of when to choose it over costs_and_help or search_residences. No exclusions or preconditions are given.

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