Skip to main content
Glama

Résidences Montréal

Costs and financial help

costs_and_help
Read-onlyIdempotent

What it costs to live in a seniors' residence in Québec: what the register says about RPA prices, the 2026 maximum contribution for a public CHSLD, and guides on costs and financial help 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": "costs_and_help"
  }
}

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

A3.5/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 useful provenance by naming its sources (the register, residences-montreal.com) and pinning a specific figure year (2026), but says nothing about freshness, coverage limits, or whether answers are static or generated.

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 that puts the core subject first and then enumerates the three content areas. Dense and waste-free, though the trailing list is somewhat run-on and could have been split for scannability.

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 not be explained, and the description covers scope, sources, and two specific data points. For a one-parameter read-only lookup tool this is close to complete, with only the question of how it relates to the guide-finding sibling left open.

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 carries the semantics. The description adds no information about the parameter or its default, which is acceptable at this coverage level but earns only the baseline.

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 states a specific subject ('what it costs to live in a seniors' residence in Québec') and enumerates the concrete content returned: RPA prices from the register, the 2026 maximum contribution for a public CHSLD, and cost/financial-help guides. It is clearly an information-retrieval tool rather than a search or comparison tool, though it never explicitly distinguishes itself from siblings like find_guides or compare_residences.

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 'ask this when the user wants cost or financial-help information.' There is no explicit when-to-use statement, no exclusion of the overlapping find_guides tool despite the description mentioning guides, and no note on whether it answers questions or returns links.

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