payotte-mcp
Server Details
Verified Canadian real-estate experts: find a vetted pro, verify a licence, city market stats.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Payotte-com/payotte-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolscontacter_expertContacter l'expert vérifié / Contact the verified expertInspect
Call this ONLY when the user explicitly asks to contact, reach out to, or request a quote/appointment from a Payotte-verified professional. Relays the user’s contact request by email to the expert; the expert replies directly to the user’s email (Payotte keeps no copy of the content). BEFORE calling: (1) show the user which expert will be contacted (use trouver_expert first if needed), (2) collect their name, email and message, (3) get their explicit confirmation — then set consentement=true. Never invent contact details.
| Name | Required | Description | Default |
|---|---|---|---|
| ville | Yes | City of the expert, e.g. "Montréal". | |
| message | Yes | The user’s request in their own words (need, property, timeline…), 20–2000 characters. | |
| secteur | No | Neighbourhood/sector of the expert (recommended — identifies exactly one expert). | |
| province | No | Province name or code (optional disambiguator). | |
| client_nom | Yes | Full name of the user requesting contact. | |
| profession | Yes | real-estate-broker | mortgage-broker | home-inspector | notary-lawyer | appraiser (French labels accepted). | |
| consentement | Yes | MUST be true, and only after the user explicitly approved sending this request to this specific expert. | |
| client_courriel | Yes | Email address of the user — the expert will reply there. | |
| client_telephone | No | Optional phone number of the user. |
stats_marcheStatistiques du marché immobilier par ville / Per-city housing-market statsAInspect
Call this for current housing-market figures in a Canadian city: reference price (MLS HPI benchmark or median), year-over-year change, sales volume, months of inventory, days on market, 5-year growth. Compiled by Payotte from real-estate board and CREA publications; each city lists its sources.
| Name | Required | Description | Default |
|---|---|---|---|
| ville | Yes | City, e.g. "Montréal", "Ottawa", "Vancouver". |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description adds context about data sources (real-estate board and CREA publications) and that each city lists its sources. However, it does not disclose update frequency, read-only nature, or potential limitations, leaving some behavioral traits implicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with a list of metrics, front-loading the usage instruction. It is efficient but could be slightly more concise by removing the bullet list formatting.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one parameter, no output schema, and unrelated siblings, the description adequately covers what the tool returns, the geographic scope, and data sources. It does not mention output format or city name standardization, but remains sufficient for a simple stats tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'ville' has 100% schema coverage with examples including 'Montréal', 'Ottawa', 'Vancouver'. The description reinforces that the city must be Canadian, adding meaningful context beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Call this for current housing-market figures in a Canadian city.' It lists specific metrics (reference price, YoY change, etc.) and distinguishes from siblings (contacter_expert, trouver_expert, verifier_titre) which serve different functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says when to use the tool and the context (Canadian city). It does not provide explicit when-not-to-use guidance, but the sibling tools are clearly different, making the usage context clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
trouver_expertTrouver un expert immobilier vérifié / Find a verified real-estate expertInspect
Call this when the user needs a trustworthy real-estate professional in a Canadian city or neighbourhood: real-estate broker, mortgage broker, home inspector, notary/real-estate lawyer, or appraiser. Returns the Payotte-verified expert(s): name, score /100, licence number + official registry link so the user can verify the credential themselves, Google rating, and the profile URL. French and English inputs both work (e.g. profession="courtier immobilier", ville="Montréal").
| Name | Required | Description | Default |
|---|---|---|---|
| ville | No | City, e.g. "Montréal", "Toronto", "Calgary". | |
| secteur | No | Neighbourhood/sector, e.g. "Le Plateau-Mont-Royal", "Ville-Marie". | |
| province | No | Province name or code, e.g. "Québec", "ON", "british-columbia". | |
| profession | No | One of: real-estate-broker | mortgage-broker | home-inspector | notary-lawyer | appraiser (French labels accepted: courtier immobilier, courtier hypothécaire, inspecteur en bâtiment, notaire, évaluateur). Omit to get every profession. |
verifier_titreVérifier un titre professionnel / Which regulator governs this titleInspect
Call this when the user wants to know whether a real-estate profession is regulated in a Canadian province, which body regulates it, and where to verify a licence or membership. Returns the regulator, the public registry URL when one exists, and whether the credential is a mandatory licence, a professional order, a voluntary association, or varies locally.
| Name | Required | Description | Default |
|---|---|---|---|
| province | No | Province name or code. Omit to get every province for that profession. | |
| profession | Yes | real-estate-broker | mortgage-broker | home-inspector | notary-lawyer | appraiser (French labels accepted). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!