Skip to main content
Glama

payotte-mcp

by io.github.Payotte-com

Acheter ou louer ? / Rent vs buy in a city

acheter_ou_louer

Call this when the user wonders whether to rent or buy in a Canadian city. Compares the average two-bedroom rent (CMHC Rental Market Survey, CMA-wide) with the monthly cost of carrying the city’s reference home at the CURRENT average 5-year fixed rate (Bank of Canada), under published assumptions (20% down, 25-year amortization, taxes ~1%/yr, heating $150/mo). Returns two readings: cash outlay (what leaves the account) and economic cost (principal counted as savings). Only cities inside a CMHC-covered metro have rent data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
villeYesCity, e.g. "Montréal", "Toronto", "Winnipeg".

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It thoroughly discloses data sources (CMHC, Bank of Canada), assumptions (20% down, 25-year amortization, etc.), and return values (cash outlay vs economic cost). There is no contradiction with annotations.

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?

The description is a single, front-loaded paragraph of four sentences. It efficiently conveys the tool's purpose, inputs, assumptions, and outputs without unnecessary words.

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

Completeness5/5

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

Given the tool's single parameter and no output schema, the description fully covers what the agent needs: when to use, what data is used, assumptions, and what the tool returns. It also addresses the limitation about CMHC coverage.

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% for the single parameter 'ville', and the schema provides a basic example. The tool description does not add additional semantics beyond what the schema already provides, so it earns the baseline score of 3.

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

Purpose5/5

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

The description explicitly states that the tool compares renting vs buying in a Canadian city, using specific metrics (average rent and carrying cost). It uniquely addresses the rent vs buy question, distinguishing it from sibling tools like taux_courants or contacter_expert.

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

Usage Guidelines4/5

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

The description clearly states when to call the tool ('when the user wonders whether to rent or buy in a Canadian city') and notes a limitation ('Only cities inside a CMHC-covered metro have rent data'). It implies when not to use (if city is not covered), but does not provide explicit alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All payotte-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct facet of Canadian real estate: rent-vs-buy, income qualification, market stats, rates, land-transfer tax, expert search, expert contact, and credential verification. The descriptions clearly separate the purposes, so an agent can confidently select the right tool without ambiguity.

Naming Consistency4/5

Tool names are uniformly in French and use underscores, but they mix verb-noun constructions (contacter_expert, trouver_expert, verifier_titre) with noun-phrase labels (salaire_requis, taux_courants, taxe_mutation, stats_marche). This is readable and mostly predictable, though not a single consistent pattern.

Tool Count5/5

With 8 tools, the server is well-scoped for its purpose. Each tool handles a meaningful and non-trivial calculation or lookup, and there are no redundant or filler tools. The count sits comfortably in the ideal range.

Completeness4/5

The server covers the core home-buying journey: market data, rates, affordability, purchase costs, and expert connection. Minor gaps exist (e.g., no mortgage payment calculator or rent cost estimator beyond the buy-vs-rent comparison), but agents can work around these by combining existing tools.

Resources