Skip to main content
Glama
sedis-ab

@sedis/mcp

Official
by sedis-ab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Search your property units (Fastighet)

fastighetsbenchmark_search_property_units
Read-only

Find property units by name, property type, municipality, or comparison-zone membership and obtain their sedisIds for time-series comparison.

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
NameRequiredDescriptionDefault
langNoLanguage for names/descriptions; English default, 'sv' for Swedish.
pageNo1-indexed result page (first page = 1), e.g. 1.
sortNoComma-separated sort fields; prefix '-' for descending, e.g. '-name'.
pageSizeNoRows per page (v2 default 50, max 500), e.g. 50.
nameContainsNoCase-insensitive property-unit-name fragment, e.g. 'Office'.
propertyTypeNoProperty-type id (int, NOT a name); discover ids from find_parameter enumValues, e.g. 1 = Kontor/Office.
municipalityIdNoMunicipality id to filter by, e.g. 180 (Stockholm).
includeGeometryNofalse (default, lean) omits geometry; true opts the heavy geometry member into the response via ?fields=.
propertyTypeNameNoProperty-type by NAME (locale-aware), e.g. 'Office'/'Kontor'; alternative to the numeric propertyType id.
belongsToJamforelseobjektSedisIdNoComparison-zone sedisId (from list_jamforelseobjekt) — returns only your units in that zone, e.g. 'JO-A'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesYour matching property units (Fastighet).
pageYesThe page you are on (1-indexed).
pageSizeNoRows per page echoed back by v2, e.g. 50.
totalCountNoTotal matching rows across all pages; null/absent when count is skipped.
totalPagesNoTotal page count; null/absent when count is skipped.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds critical behavior: tenant scoping ('Tenant-scoped to your data'), explicit read-only assurance ('never writes'), and default geometry omission. No contradiction 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 dense but every sentence carries operational value: purpose, workflow, defaults, example, and scoping. It is front-loaded with the most critical info and avoids filler.

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?

With an output schema present and 10 optional parameters, the description covers purpose, usage flow, parameter semantics via example, default behavior, and tenant scoping. It provides everything an agent needs to select and invoke the tool correctly.

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 covers all parameters with descriptions (100%), so baseline is 3. The description adds value with a concrete example ('propertyType 1 (Office), belongsToJamforelseobjektSedisId 'JO-A'') and clarifies the relationship between propertyType and propertyTypeName, as well as the role of belongsToJamforelseobjektSedisId in the flow.

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 clearly states the verb ('Find') and resource ('your property units') with specific filter dimensions (name, property-type id, municipality, comparison-zone membership). It distinguishes itself from siblings by positioning as the 'object-finding step' in the §8 A6 flow.

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?

Explicitly describes the full workflow: take a comparison zone from fastighetsbenchmark_list_jamforelseobjekt, filter with belongsToJamforelseobjektSedisId, and pass sedisIds to fastighetsbenchmark_get_comp_timeseries. Also notes the lean default and includeGeometry toggle.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sedis-ab/sedis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server