Skip to main content
Glama

get_property_price_index

Read-onlyIdempotent

Retrieve Switzerland’s BFS residential property price index (IMPI) by quarter, date range, and property type (houses or apartments) to analyze housing price trends.

Instructions

BFS residential property price index (IMPI), quarterly since 2017Q1, Q4 2019 = 100

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
toNoInclusive, e.g. 2024Q4 or 2024 (default: latest)
fromNoInclusive, e.g. 2020Q1 or 2020 (default: earliest)
typeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.0
    • changedInput schema / properties / from / description
      Previous value: -"Start period (inclusive). Format: \"2020Q1\", \"2020-Q1\", or just \"2020\". Defaults to earliest available (2009-Q4)."New value: +"Inclusive, e.g. 2020Q1 or 2020 (default: earliest)"
    • changedInput schema / properties / to / description
      Previous value: -"End period (inclusive). Format: \"2024Q4\", \"2024-Q4\", or just \"2024\". Defaults to latest available."New value: +"Inclusive, e.g. 2024Q4 or 2024 (default: latest)"
    • addedInput schema / properties / type / default
      Added value: +"all"
    • removedInput schema / properties / type / description
      Removed value: -"Property type to filter by: \"all\" (combined index), \"houses\" (single-family), \"apartments\" (condominiums/flats). Defaults to \"all\"."
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "all",
      +  "houses",
      +  "apartments"
      +]
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuine domain context beyond that: publisher (BFS), cadence (quarterly), coverage start (2017Q1), and the index base (Q4 2019 = 100), which is essential for interpreting returned values. It does not say whether values are nominal or real, or whether the series is seasonally adjusted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler; the index base and coverage window are front-loaded. It is efficient but fragmentary, lacking a verb and any structural separation between what it returns and how to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, three parameters (one an undocumented enum), and no return-value documentation, the description should do more: it never states the unit of the returned values (index points), the field names, or the granularity per canton/municipality. The base-period note is helpful but insufficient for a data-retrieval tool whose output shape is undocumented.

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

Parameters2/5

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

Schema description coverage is 67%, with from/to carrying examples and default semantics in the schema. The description adds no parameter meaning whatsoever, and the 'type' enum (all/houses/apartments) has no description in either the schema or the description, leaving the agent to infer what those categories mean.

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

Purpose3/5

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

The description identifies the resource (BFS residential property price index / IMPI) but is a noun phrase with no verb, so an agent must infer that it retrieves index values. It adds useful scope details (quarterly, since 2017Q1, Q4 2019 = 100) but does not distinguish itself from siblings such as get_rent_index or search_real_estate_data.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the closest alternatives (get_rent_index, search_real_estate_data), and no exclusions. The agent is left to guess whether this is the right price-index tool versus a rental or listing-data tool.

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