Skip to main content
Glama

Swiss residential property price index

get_property_price_index
Read-only

Retrieve Switzerland's quarterly residential property price index (IMPI) for all homes, single-family houses, and owner-occupied apartments, including year-on-year and period changes.

Instructions

The FSO residential property price index (IMPI, Q4 2019 = 100), quarterly from 2017: all residential property, single-family houses and owner-occupied apartments, with year-on-year change and change over the selected period. Purchase prices, not rents. Examples: {} (latest 8 quarters), {from:'2020', to:'2025-Q2'}.

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_property_price_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period, e.g. 2025 or 2025-Q2
fromNoFirst period, e.g. 2020 or 2020-Q1
lastNoQuarters to return when from/to are not given

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuine context beyond them: coverage starts in 2017, frequency is quarterly, only purchase (not rental) prices are returned, and each record carries year-on-year change plus change over the selected period. It does not mention rate limits or how missing/partial periods are handled, but for a read-only statistical endpoint that is a minor omission.

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?

One dense but well-ordered sentence leads with the index identity and base period, then coverage, then what is returned, followed by two compact invocation examples. Every clause carries information the agent needs; nothing is padded or restated from the schema.

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?

With no output schema, the description carries the burden of describing returns and does so in outline: index level plus year-on-year and period-over-period change. For a three-parameter read-only tool with fully documented parameters and clear annotations, this is close to complete, though it omits units and the shape of the returned series.

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% — 'from', 'to' and 'last' all carry patterns, defaults and bounds — so the schema already does the heavy lifting. The examples only restate behavior implied by the 'last' default of 8, adding no new semantics such as inclusive/exclusive period boundaries or how the period-change is computed.

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?

Names a precise resource — the FSO residential property price index (IMPI), base Q4 2019 = 100 — and states the verb/scope (quarterly retrieval from 2017) plus the sub-series covered (all residential property, single-family houses, owner-occupied apartments). The explicit 'Purchase prices, not rents' eliminates the most likely confusion with another price series, so an agent can identify the tool's output without any other context.

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 gives concrete invocation patterns: '{}' for the latest 8 quarters and '{from: 2020, to: 2025-Q2}' for a bounded range, which tells an agent how to call it in the two common situations. It stops short of stating exclusions or pointing to alternatives, but there is no obvious competing sibling for this data.

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

Deploy Server

Other Tools