Skip to main content
Glama

Résidences Montréal

List areas covered

list_areas
Read-onlyIdempotent

The cities and neighbourhoods of the island of Montréal with residences in the register, with counts, and the neighbourhood guides 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": "list_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer: 'fr' or 'en'.en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered structurally. The description adds the geographic scope (island of Montréal) and that results include counts and guides, but says nothing about ordering, completeness, or freshness with respect to the register.

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 compact sentence with no filler, and the core content (areas with counts) leads. It is a grammatical fragment rather than a verb-led statement, which slightly reduces immediate clarity about the action performed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations and an output schema, return values need not be explained, and the geographic scope is stated. What is missing is any routing signal relative to the five sibling tools, which matters for a discovery-style listing endpoint.

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?

There is a single optional 'language' parameter with an enum and 100% schema description coverage, so the schema fully documents it. The description adds no meaning about language behavior (e.g., whether guide content is localized), so the baseline of 3 applies.

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 names the concrete resource: cities and neighbourhoods of Montréal with registered residences, plus counts and neighbourhood guides. It is clear what the tool returns, but it does not distinguish itself from siblings such as find_guides, which the mention of 'neighbourhood guides' could overlap with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this tool instead of search_residences or find_guides, and no stated prerequisites or exclusions. The agent must infer usage purely from the noun phrase describing the content.

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