@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Find a Fastighetsbenchmark parameter

fastighetsbenchmark_find_parameter

Read-only

Find real-estate benchmark parameters by name fragment or group; returns code, dataType, and enum values to use in comp timeseries queries.

Instructions

Read-only. Discover the right real-estate benchmark parameter by name fragment or group and return each parameter's code, English name, dataType (decimal/boolean/enum/date) and — for enum parameters — its enumValues legal-value domain. Use this to resolve the parameterCode you pass to fastighetsbenchmark_get_comp_timeseries, and read dataType to know which CompDatum value member to trust. Example: nameContains 'Total return'. Shared reference 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'.
`group`	No	Parameter group name to filter by, e.g. 'Return'.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`nameContains`	No	Case-insensitive parameter-name fragment, e.g. 'Total return'.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Matching Fastighetsbenchmark CompParameters.
`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.

Changed10 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 / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / groupName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / groupName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / isBaseData / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / isBaseData / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / unit / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / unit / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv1.1.5Aug 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description reinforces the readOnlyHint with 'Read-only' and 'Shared reference data; never writes', and gives a concrete sense of the operation's effect (a lookup returning parameter metadata). It does not mention pagination or performance, but the read-only reference nature is clear and consistent with annotations.

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 compact, front-loads the read-only nature and purpose, explains output fields, gives an example, and states the relationship to the downstream tool. It avoids unnecessary prose while preserving the key operational details.

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 the readOnlyHint/openWorldHint annotationshola and a 100%-documented schema, the description covers the tool's role, how its results are consumed, and the meaning of `dataType`. No important missing context stands out for an agent selecting or invoking this tool.

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?

The input schema already covers all parameters with descriptions and examples, and the description adds usage context by naming `nameContains`-style substring matching. However, it does not map each query parameter to the discovery workflow beyond the overall example, so value added over the structured schema is modest.

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 action ('Discover') with a clear resource ('real-estate benchmark parameter') and lists the returned fields (`code`, English name, `dataType`, enumValues). It also distinguishes this tool from the downstream consumer `fastighetsbenchmark_get_comp_timeseries` by explaining how the output is used.

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 clearly says to use it to resolve the `parameterCode` passed to `fastighetsbenchmark_get_comp_timeseries` and to read `dataType` to decide which CompDatum member to trust. It does not explicitly contrast with sibling lookup/search tools, but it gives strong contextual guidance for the main workflow.

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

Deploy Server