@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List your comparison zones (Jämförelseobjekt)

fastighetsbenchmark_list_jamforelseobjekt

Read-only

Retrieve your real-estate comparison zones by name to get each zone's sedisId, then use that ID to search property units within the zone. Read-only and tenant-scoped.

Instructions

Read-only. List YOUR comparison zones (Jämförelseobjekt — your clones of a Sedis-owned aggregate), returning each zone's sedisId. This is the FIRST step of the §8 A6 flow: find a zone by name here, then pass its sedisId to fastighetsbenchmark_search_property_units as belongsToJamforelseobjektSedisId to find your units in it. Lean by default: set detail: true to opt into the tenant-filtered containsPropertyUnits lineage. Example: nameContains 'Stockholm'. Tenant-scoped to your data; read-only — never writes.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-indexed result page (first page = 1), e.g. 1.
`sort`	No	Comma-separated sort fields; prefix '-' for descending, e.g. '-name'.
`detail`	No	false (default, lean) omits lineage; true opts the tenant-filtered containsPropertyUnits array in via ?fields=.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`nameContains`	No	Case-insensitive comparison-zone-name fragment, e.g. 'Stockholm'.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Your comparison zones (Jämförelseobjekt).
`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.

Changed7 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#"

changedOutput schema / properties / data / items / properties / containsPropertyUnits / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "description": "Referenced Comp display name, e.g. 'Office tower 1'."
-        },
-        "sedisId": {
-          "description": "Referenced Comp sedisId; resolve via get_comp_timeseries / search, e.g. 'PU-1'.",
-          "type": "string"
-        }
-      },
-      "required": [
-        "sedisId"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "name": {
+          "description": "Referenced Comp display name, e.g. 'Office tower 1'.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "sedisId": {
+          "description": "Referenced Comp sedisId; resolve via get_comp_timeseries / search, e.g. 'PU-1'.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "sedisId"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only' and 'never writes'. It adds useful behavioral context beyond the annotations: the list is tenant-scoped to the caller's data, and `detail: true` opts into a tenant-filtered `containsPropertyUnits` lineage. There is no contradiction with the annotations.

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?

The description is information-dense and front-loaded with the key facts: read-only, ownership, and result content. It flows logically from purpose to workflow to detail behavior to example. The only mild issue is that 'read-only' is stated twice, once at the start and again at the end.

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?

Given that the output schema exists and all optional parameters are fully documented in the input schema, the description only needs to supply context, and it does thoroughly: ownership, tenant scoping, default lean behavior, a concrete example, and exact next-step parameter mapping. Nothing needed to invoke or chain the tool correctly 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 description coverage is 100%, so the schema already documents all five parameters and the baseline is 3. The description adds value with a concrete `nameContains` example ('Stockholm') and explains how the returned `sedisId` feeds the downstream parameter `belongsToJamforelseobjektSedisId`, which is not present in this tool's schema.

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 opens with a specific verb and resource: 'List YOUR comparison zones', and clarifies that Jämförelseobjekt are 'your clones of a Sedis-owned aggregate' returning `sedisId`. It also positions the tool as the 'FIRST step of the §8 A6 flow' and names the downstream sibling, making it easy for an agent to distinguish from related list/search tools.

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 explicit usage context: use this as the first step of the A6 flow, find a zone by name, then pass its `sedisId` to `fastighetsbenchmark_search_property_units`. It does not explicitly name a 'when-not-to-use' alternative such as `fastighetsbenchmark_list_reference_zones`, but the ownership contrast ('YOUR' vs 'Sedis-owned') provides enough directional guidance.

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

Deploy Server