@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List listed companies (Bolagsanalys)

bolagsanalys_list_companies

Read-only

Search listed companies by name or country code to retrieve their company IDs for fetching quarterly financial data.

Instructions

Read-only. Search Sedis's catalog of listed companies by name fragment or country code and return each company's companyId and name. This is the FIRST step of the Bolagsanalys flow: take a companyId from here and pass it to bolagsanalys_get_data to fetch its quarterly figures. Example: nameContains 'Volvo', countryCode 'SE'. Reference data shared across all tenants; this tool never writes or ingests.

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.
`countryCode`	No	ISO-3166 alpha-2 country code, e.g. 'SE'.
`nameContains`	No	Case-insensitive company-name fragment, e.g. 'Volvo'.

Output Schema

TableJSON Schema

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

Changed8 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 / countryCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / countryCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / isInactive / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / isInactive / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / nextReportDate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / nextReportDate / 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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable context beyond the annotations: it is reference data shared across all tenants and 'never writes or ingests', which reinforces what an agent can rely on. No contradictory or missing critical behavior is apparent given the read-only nature.

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-loaded with the read-only safety indicator and the core search action, then enriched with the flow context and a concrete example. Every sentence contributes meaningful information with no filler or redundant restatement of the tool name.

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 output schema exists and annotations cover read-only/open-world behavior, the description completes the picture with the Bolagsanalys flow position, the use of the returned companyId, and an illustrative query example. Nothing an agent needs to invoke this tool 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 five parameters in detail. The description adds a useful semantic grouping ('by name fragment or country code') and a concrete example (nameContains 'Volvo', countryCode 'SE'), but it does not need to compensate for any schema gap. 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 ('Search'), a precise resource ('Sedis's catalog of listed companies'), and the two filter dimensions (name fragment, country code). It also distinguishes itself from sibling bolagsanalys_get_data by positioning itself as the first step of the flow, so an agent can tell them apart without opening schemas.

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 clear contextual guidance: it is the FIRST step of the Bolagsanalys flow and the returned companyId is meant to be passed to bolagsanalys_get_data. It does not explicitly enumerate when to avoid this tool in favor of siblings like bolagsanalys_search_data, but the flow-level instruction is strong and practical.

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

Deploy Server