Skip to main content
Glama

Résidences Montréal

Explain RPA categories

explain_rpa_categories
Read-onlyIdempotent

What Québec's four categories of private seniors' residences (RPA) mean, who each is for, and what the service types (meals, domestic help, security, recreation, personal assistance, nursing care) cover, from the certification regulation.

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": "explain_rpa_categories"
  }
}

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.7/5.0
Behavior4/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 the safety profile is covered. The description adds genuinely new behavioral context: the content is authoritative and sourced from the certification regulation and scoped to Québec. It does not discuss caching, length, or language behavior, but nothing material is omitted for a static reference lookup.

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?

One sentence, front-loaded with the subject (the four RPA categories) before the parenthetical service-type list. The enumeration is long but each item is substantive rather than padding. It is dense but not wasteful.

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 reference tool with one optional enum parameter and a published output schema, the description is essentially complete: it states the scope, the source, and the topics the answer spans. Return format needn't be explained given the output schema, and only the language dimension is left unaddressed in prose.

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 description coverage is 100% and the single language parameter carries its own enum values, default, and explanation, so the schema does the work. The description never mentions language at all, adding no meaning beyond the schema — baseline 3.

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 a specific resource — Québec's four RPA categories — and enumerates the content delivered: what each category means, who it is for, and what the six service types cover. That is far more than a restatement of the name, and it is plainly distinct from the retrieval/comparison siblings. It lacks an explicit 'not to be confused with' routing clause, which keeps it at 4.

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 reference/definitions tool to consult before or alongside search_residences or compare_residences, since it returns no residence records. There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of when the answer would be insufficient on its own.

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