Skip to main content
Glama

swiss-living-index

Mortgage reference rate

get_reference_rate
Read-onlyIdempotent

Swiss mortgage reference interest rate for rents (BWO/FOH): current rate, valid since, next publication dates, every change since 2008, and the rule for rent adjustments (VMWG Art. 13). Optional lease_rate (the rate in the lease) returns the quarter-point steps since then. Also returns the latest BFS rent price index (quarterly change, annual change, share of rents up/down/unchanged).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reference_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
lease_rateNoreference rate stated in the lease, e.g. 1.75

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description does not need to repeat safety basics. It usefully adds behavioral context: the optional lease_rate returns quarter-point steps since the lease rate, and the response also includes BFS rent price index figures.

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 front-loaded with the core resource and scope, then efficiently enumerates returned data and the optional parameter behavior. It contains no filler and every clause contributes useful selection or invocation context.

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?

There is no output schema, so the description must explain return values, and it does so comprehensively: current rate, valid-since date, publication dates, historical changes, legal rule, lease-rate step behavior, and BFS rent index metrics. This is sufficient for an agent to understand what the tool provides.

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%, and the schema already defines lease_rate with an example. The description goes beyond the schema by explaining the observable effect of supplying lease_rate: it returns the quarter-point steps since that rate.

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

Purpose4/5

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

The description states a specific resource and scope: the Swiss mortgage reference interest rate for rents under BWO/FOH and VMWG Art. 13. It clearly distinguishes this from generic mortgage-rate data by emphasizing rent relevance, but it does not explicitly name or rule out the nearby siblings mortgage_rates and rent_index.

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

Usage Guidelines3/5

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

Usage is implied by phrases like 'for rents' and 'rule for rent adjustments', which tell an agent the broad context. However, there is no explicit when-to-use guidance versus alternatives such as mortgage_rates or rent_index, so the agent must infer the correct routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources