Skip to main content
Glama

payotte-mcp

by io.github.Payotte-com

Taux d'intérêt canadiens courants / Current Canadian interest rates

taux_courants

Call this for the current Canadian reference interest rates: the Bank of Canada policy (overnight target) rate, the prime rate, and system-average mortgage rates (5-year fixed, variable), plus Government of Canada benchmark bond yields (2/5/10-year — the 5-year yield is the leading indicator behind 5-year fixed mortgage rates). Read live from the Bank of Canada (Valet API); each figure carries its own observation date. Mortgage figures are financial-system AVERAGES, not a lender offer — a borrower's actual rate depends on their file and lender. Source: Bank of Canada.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that data is read live from Bank of Canada API, each figure has its own observation date, and mortgage figures are system averages, not offers. This gives essential interpretation context.

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?

Four sentences, each adding substantive information: content enumeration, data source, caveat, attribution. No filler.

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?

For a zero-parameter read-only tool, the description covers content, source, freshness, and interpretation caveat. No output schema needed since values are standard interest rates.

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?

Tool has zero parameters, so schema coverage is complete. Baseline 4 applies; description adds no parameter-specific info needed.

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?

Clearly specifies the tool returns current Canadian reference interest rates, listing exact instruments (policy rate, prime, mortgage averages, bond yields). The verb 'Call this for' and specific list distinguish it from sibling real-estate tools.

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 begins with 'Call this for...' and enumerates the exact use case. No alternatives are mentioned, but sibling tools cover other real-estate topics, so the context is unambiguous.

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