@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Search your property units (Fastighet)

fastighetsbenchmark_search_property_units

Read-only

Find your property units by name, type, municipality, or comparison zone, returning each unit's sedisId for subsequent queries.

Instructions

Read-only. Find YOUR property units (Fastighet) by exact name, name fragment, property-type id, municipality, or comparison-zone membership, returning each unit's sedisId — the stable, case-sensitive key to use in every later call. name is the customer's own designation; an official property designation (fastighetsbeteckning, e.g. 'Klara 1:1') is not a name and is not searchable. Look up property-type and municipality ids with fastighetsbenchmark_list_property_types / fastighetsbenchmark_list_municipalities. This is the §8 A6 flow's object-finding step: take a comparison zone from fastighetsbenchmark_list_jamforelseobjekt and filter here with belongsToJamforelseobjektSedisId, then pass the resulting sedisIds to fastighetsbenchmark_get_comp_timeseries via sedisIdIn. Lean by default: geometry is omitted unless you set includeGeometry: true. Example: propertyType 2, belongsToJamforelseobjektSedisId 'JO-A'. Tenant-scoped to your data; read-only — never writes.

Input Schema

Name	Required	Description
`lang`	No	Language for names/descriptions; English default, 'sv' for Swedish.
`name`	No	Exact property-unit name (your own designation), case-insensitive — returns that one unit, e.g. 'Kontoret Gladan 4'.
`page`	No	1-indexed result page (first page = 1), e.g. 1.
`sort`	No	Comma-separated sort fields; prefix '-' for descending, e.g. '-name'.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`nameContains`	No	Case-insensitive property-unit-name fragment, e.g. 'Office'.
`propertyType`	No	Property-type id (int, NOT a name); look ids up with fastighetsbenchmark_list_property_types, e.g. 2.
`municipalityId`	No	Municipality id to filter by; look ids up with fastighetsbenchmark_list_municipalities (e.g. Stockholm = 21).
`includeGeometry`	No	false (default, lean) omits geometry; true opts the heavy geometry member into the response via ?fields=.
`propertyTypeName`	No	Property-type by NAME (locale-aware), e.g. 'Office'/'Kontor'; alternative to the numeric propertyType id.
`belongsToJamforelseobjektSedisId`	No	Comparison-zone sedisId (from list_jamforelseobjekt) — returns only your units in that zone, e.g. 'JO-A'.

Output Schema

Name	Required	Description
`data`	Yes	Your matching property units (Fastighet).
`page`	Yes	The page you are on (1-indexed).
`pageSize`	No	Rows per page echoed back by v2, e.g. 50.
`totalCount`	No	Total matching rows across all pages; null/absent when count is skipped.
`totalPages`	No	Total page count; null/absent when count is skipped.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.2.0Oct 6, 2026

changedInput schema / properties / municipalityId / description

Previous value: -"Municipality id to filter by, e.g. 180 (Stockholm)."New value: +"Municipality id to filter by; look ids up with fastighetsbenchmark_list_municipalities (e.g. Stockholm = 21)."

addedInput schema / properties / name

Added value: +{
+  "description": "Exact property-unit name (your own designation), case-insensitive — returns that one unit, e.g. 'Kontoret Gladan 4'.",
+  "type": "string"
+}

changedInput schema / properties / propertyType / description

Previous value: -"Property-type id (int, NOT a name); discover ids from find_parameter enumValues, e.g. 1 = Kontor/Office."New value: +"Property-type id (int, NOT a name); look ids up with fastighetsbenchmark_list_property_types, e.g. 2."

addedOutput schema / properties / data / items / properties / address

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "countryCode": {
+          "description": "ISO 3166-1 alpha-2 country, e.g. 'SE'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "postalCode": {
+          "description": "Postal code, e.g. '111 57'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "postalTown": {
+          "description": "Postal town, e.g. 'Stockholm'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "streetNameAndNumber": {
+          "description": "Street name and number, e.g. 'Sveavägen 12'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The unit's postal address { streetNameAndNumber, postalCode, postalTown, countryCode }."
+}

addedOutput schema / properties / data / items / properties / municipality

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "code": {
+          "description": "Official municipality code (Sweden: SCB kommunkod), e.g. '0180'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Municipality id; use as the municipalityId filter, e.g. 21.",
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "name": {
+          "description": "Municipality name, e.g. 'Stockholm'.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The unit's municipality as { id, name, code }."
+}

removedOutput schema / properties / data / items / properties / municipalityId

Removed value: -{
-  "anyOf": [
-    {
-      "maximum": 9007199254740991,
-      "minimum": -9007199254740991,
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Municipality id."
-}

Changed6 schema fields changedv1.1.6Sep 10, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / properties / data / items / properties / lastUpdatedUtc / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / lastUpdatedUtc / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv1.1.5Aug 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description usefully reinforces it ('never writes') and adds real behavioral context the annotations do not carry: tenant scoping to 'your data', a lean-by-default response with geometry opt-in, and the important constraint that an official fastighetsbeteckning is not a name and is not searchable. It does not cover pagination limits or ordering guarantees, but those live in the schema.

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?

Front-loaded with the highest-value facts (read-only, what it finds, the sedisId key) and then the flow context; every sentence carries routing or semantic information. It is a dense single paragraph rather than a skimmable list, and 'Read-only' / 'read-only — never writes' is mildly redundant.

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 an 11-parameter, zero-required search tool with an output schema present, the description covers purpose, id-resolution dependencies, downstream handoff, scoping, and the geometry-lean default — everything needed to invoke it correctly without explaining return values. Minor omissions (pagination defaults, sort behavior) are already documented in the schema.

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%, so the baseline is 3, but the description adds conceptual semantics beyond the field docs: sedisId is described as the stable, case-sensitive key to use in every later call, name is the customer's own designation (not the official designation), and belongsToJamforelseobjektSedisId is framed as the zone-to-units bridge. The worked example (propertyType 2, 'JO-A') further anchors usage.

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?

States a specific verb (find/search) and resource (YOUR property units / Fastighet) plus the exact match modes accepted: exact name, name fragment, property-type id, municipality, comparison-zone membership. It also explicitly distinguishes itself from siblings by naming the id-lookup tools and the downstream consumer (get_comp_timeseries), so an agent can place it in the pipeline without opening any schema.

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?

Gives explicit when-to-use routing: it is 'the §8 A6 flow's object-finding step', take a comparison zone from list_jamforelseobjekt, filter here with belongsToJamforelseobjektSedisId, then pass the resulting sedisIds to get_comp_timeseries via sedisIdIn. It also names the alternatives for id resolution (list_property_types, list_municipalities), leaving nothing to inference.

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

Deploy Server