Skip to main content
Glama

payotte-mcp

by io.github.Payotte-com

Salaire requis pour acheter / Income needed to buy in a city

salaire_requis

Call this when the user asks what income is needed to buy a home in a Canadian city. Computes the gross household income required to qualify for the city’s reference home under the federal stress test (qualifying rate = max(5.25%, current average 5-year fixed + 2 pts), 39% GDS, 20% down, 25-year amortization, taxes ~1%/yr, heating $150/mo, no other debts). Same published methodology as payotte.com/salaire-pour-acheter-une-maison-canada. A theoretical qualification threshold, not a loan offer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prixNoOptional price in CAD to test instead of the city’s reference price.
villeYesCity, e.g. "Montréal", "Vancouver", "Halifax".

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior. It details the calculation methodology (stress test, GDS ratio, down payment, amortization, taxes, heating), cites a public source for methodology, and clarifies it is a theoretical threshold, not a loan offer. All relevant behavioral traits are covered.

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 concise (around 4 lines) and front-loaded with the usage trigger. Every sentence adds value: trigger, methodology summary, source reference, and caveat. No unnecessary words.

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?

Given the tool's complexity (multiple assumptions) and lack of an output schema, the description explains what is computed and the methodology. It does not explicitly state the output format (likely a number), but from context it is clear. The completeness is high but could be slightly improved by specifying the return type.

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 coverage is 100%, so the baseline is 3. The description adds some context (e.g., 'prix' is optional to test an alternative price), but the schema already documents both parameters adequately. No additional semantic meaning beyond what the schema provides is present.

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 clearly states the tool's purpose: to compute the income needed to buy a home in a Canadian city. It uses a specific verb ('computes') and a specific resource ('reference home'). It distinguishes from sibling tools like acheter_ou_louer (buy vs. rent) and taux_courants (current rates), as this tool is solely for income qualification.

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 explicitly states when to use the tool: 'Call this when the user asks what income is needed to buy a home in a Canadian city.' It provides clear context but does not mention when not to use it or suggest alternatives, though sibling tool names offer some implicit differentiation.

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