Skip to main content
Glama

get_rent_index

Read-onlyIdempotent

Retrieve Switzerland's monthly consumer price index (CPI/LIK) including rents, based on December 1982 = 100, for a given year or recent months. Use get_property_price_index for purchase prices.

Instructions

BFS consumer price index (CPI/LIK, incl. rents), monthly, Dec 1982 = 100. Not a dedicated rent index; for purchase prices use get_property_price_index

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

Input Schema

NameRequiredDescriptionDefault
yearNo1982 onward (omit for recent months)
limitNoRecent months, 1–60; ignored if year set

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +24
    • changedInput schema / properties / limit / description
      Previous value: -"Number of recent monthly data points to return (1–60, default 24). Ignored if year is set."New value: +"Recent months, 1–60; ignored if year set"
    • changedInput schema / properties / year / description
      Previous value: -"Filter to a specific year (1983–2025). Omit for latest 24 months."New value: +"1982 onward (omit for recent months)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description's job is to add domain context — which it does by disclosing the data source, cadence, and index base needed to interpret the numbers. It does not describe the shape of the returned series or how gaps/partial months appear, which is the remaining gap.

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?

Two dense sentences, front-loaded with what the data actually is before the disambiguation. No filler, and every clause (source, frequency, base, exclusion, alternative) carries information.

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?

For a two-parameter, no-output-schema read tool, the description supplies the interpretive context an agent needs (what the index measures and its base). Only the return shape — a time series vs. a single point — is left implicit, inferred from the year/limit parameters.

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 description coverage is 100% and both parameters (year with the 1982-onward note, limit 1–60 ignored when year is set) are fully documented in the schema. The description adds no parameter-level meaning beyond it, so the baseline 3 applies.

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?

The description names the source and exact statistic (BFS consumer price index, CPI/LIK, including rents), its frequency, and its index base (Dec 1982 = 100). It also pre-empts the misleading tool name by stating it is not a dedicated rent index, so an agent cannot mistake its scope.

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

Usage Guidelines5/5

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

It gives an explicit exclusion plus the alternative: for purchase prices use get_property_price_index. Combined with the 'not a dedicated rent index' caveat, an agent has a clear routing rule between this and the sibling price-index 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