Skip to main content
Glama

payotte-mcp

by io.github.Payotte-com

Contacter l'expert vérifié / Contact the verified expert

contacter_expert

Call this ONLY when the user explicitly asks to contact, reach out to, or request a quote/appointment from a Payotte-listed professional. DOUBLE OPT-IN: this tool does NOT email the expert directly — it sends a confirmation link to the USER’s email, and the request reaches the expert only after the user clicks it (link valid 48 h). Tell the user to check their inbox. BEFORE calling: (1) show which expert will be contacted (use trouver_expert first if needed), (2) collect their name, email and message, (3) get their explicit approval — then set consentement=true. Never invent contact details. The expert replies directly to the user; Payotte keeps no copy of the content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
villeYesCity of the expert, e.g. "Montréal".
messageYesThe user’s request in their own words (need, property, timeline…), 20–2000 characters.
secteurNoNeighbourhood/sector of the expert (recommended — identifies exactly one expert).
provinceNoProvince name or code (optional disambiguator).
client_nomYesFull name of the user requesting contact.
professionYesreal-estate-broker | mortgage-broker | home-inspector | notary-lawyer | appraiser (French labels accepted).
consentementYesMUST be true, and only after the user explicitly approved sending this request to this specific expert.
client_courrielYesEmail address of the user — the expert will reply there.
client_telephoneNoOptional phone number of the user.

TDQS

A4.9/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 critical double opt-in behavior: the tool sends a confirmation link to the user's email, the expert is only contacted after the user clicks it, and the link is valid for 48 hours. It also details prerequisite steps, the need for explicit approval, and that Payotte keeps no copy of the content—far exceeding typical transparency.

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 densely packed with essential safety and workflow information, each sentence serving a purpose. It uses clear headings and a numbered list, making it easy to parse despite its length. No wasted 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 complexity—9 parameters, 6 required, no output schema, and no annotations—the description is exceptionally complete. It covers the full user journey, consent mechanics, privacy aspects, and potential pitfalls, leaving no critical operational detail unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaningful parameter context: it explicitly instructs setting 'consentement' to true only after explicit approval, references collecting client name/email/message, and warns against inventing contact details. This goes beyond the schema's basic descriptions.

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 function: contacting a Payotte-listed professional when the user explicitly asks to reach out or request a quote/appointment. It distinguishes itself from the sibling 'trouver_expert' by noting when to call this tool instead.

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

Usage Guidelines5/5

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

Explicitly says 'Call this ONLY when the user explicitly asks to contact, reach out to, or request a quote/appointment'. It also instructs to use 'trouver_expert' first if needed, providing clear when-to-use and alternative guidance.

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