@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List your collections (Samling)

fastighetsbenchmark_list_samlingar

Read-only

List your property-benchmark collections (Samling) by name filter, returning each collection's member company IDs for targeted timeseries queries.

Instructions

Read-only. List YOUR collections (Samling). Each row exposes its members as containingCompSedisIds — an array of ids, not nested objects — so you can reference-then-resolve: take those ids and pass them to fastighetsbenchmark_get_comp_timeseries via sedisIdIn only for the collections you actually need (this keeps payloads bounded). Example: nameContains 'Stockholm offices'. Tenant-scoped to your data; read-only — never writes (creating/replacing/deleting a Samling is not exposed here).

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'.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`nameContains`	No	Case-insensitive collection-name fragment, e.g. 'Stockholm offices'.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Your collections (Samling).
`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.4/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, and the description reinforces the read-only nature ('Read-only', 'never writes'). It adds useful behavioral context beyond the annotations: the response shape (each row exposes `containingCompSedisIds` as an array of ids, not nested objects), the reference-then-resolve pattern, and the note that creating/replacing/deleting a Samling is not exposed here. It doesn't describe pagination behavior, but the schema already documents page/pageSize defaults.

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 dense but well-structured: it front-loads the read-only nature and the core purpose, then explains the response shape and the recommended workflow, and ends with an example. Every sentence earns its place, though the workflow explanation is slightly long and could be tightened.

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 read-only list tool with a rich output schema, 100% parameter coverage, and annotations declaring read-only and open-world hints, the description is complete. It tells the agent what the tool returns, how to use the returned ids, and what the tool does not do. Nothing an agent needs to call it correctly is missing.

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%, so the schema already documents all four parameters. The description adds a concrete example for `nameContains` ('Stockholm offices') and explains the purpose of the returned ids, but it doesn't add meaning to the parameters beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb ('List'), a resource ('your collections (Samling)'), and a key differentiator: it lists the tenant's own collections, not reference zones or comparison objects. It also names the sibling tool to use for resolving the returned ids, which distinguishes it from the other list tools in the sibling set.

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 (to list your own collections) and gives a concrete workflow: take the `containingCompSedisIds` from each row and pass them to `fastighetsbenchmark_get_comp_timeseries` via `sedisIdIn` only for the collections you need. It also gives a concrete example (`nameContains 'Stockholm offices'`), which is actionable guidance.

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

Deploy Server