@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

Locate your property units by name, property type, municipality, or comparison zone and retrieve their sedisIds. Pass the returned IDs to get_comp_timeseries for benchmark analysis.

Instructions

Read-only. Find YOUR property units (Fastighet) by name, property-type id, municipality, or comparison-zone membership, returning each unit's sedisId. 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 1 (Office), belongsToJamforelseobjektSedisId 'JO-A'. Tenant-scoped to your data; read-only — never writes.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Language for names/descriptions; English default, 'sv' for Swedish.
`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); discover ids from find_parameter enumValues, e.g. 1 = Kontor/Office.
`municipalityId`	No	Municipality id to filter by, e.g. 180 (Stockholm).
`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

TableJSON 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.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.9/5.0

Behavior5/5

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

Annotations already mark the tool read-only, and the description reinforces this with 'Read-only' and 'read-only — never writes'. It adds important behavioral detail beyond the schema: tenant scoping, lean-by-default geometry behavior, and the fact that `includeGeometry: true` opts into the heavy response member.

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 dense but every clause earns its place: scope, key filters, return field, workflow position, geometry default, and tenant restriction. It front-loads the most essential information before giving examples and flow 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?

For a tool with 10 parameters, a full input schema, an output schema, and rich sibling context, the description covers what an agent needs beyond structured data: the workflow step, the default behavior, and how to chain results forward. Nothing required for correct invocation is missing.

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, and the schema already documents all 10 parameters. The description adds meaningful value on top: it explains how `belongsToJamforelseobjektSedisId` connects to the comparison-zone flow, and gives concrete examples such as propertyType 1 (Office) and 'JO-A'.

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 a specific action ('Find YOUR property units'), defines the target resource, and states the primary return value (`sedisId`). It also positions the tool as the object-finding step in the §8 A6 flow, distinguishing it from sibling tools like `fastighetsbenchmark_list_jamforelseobjekt` and `fastighetsbenchmark_get_comp_timeseries`.

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?

The description explicitly says when to use this tool and how it connects to the surrounding workflow, naming the upstream sibling (`list_jamforelseobjekt`) and downstream sibling (`get_comp_timeseries`). This is near-complete usage guidance for an object-finding step.

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

Deploy Server