@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Bolagsanalys quarterly figures

bolagsanalys_get_data

Read-only

Fetch quarterly financial figures for Swedish listed companies, optionally filtered by parameter and quarter range. Read-only access for company analysis.

Instructions

Read-only. Fetch quarterly figures for one company — optionally narrowed to a single parameter and a quarter range. Pass a companyId from bolagsanalys_list_companies and (optionally) a parameterCode from bolagsanalys_find_parameter. Quarter bounds use packed ids: quarterId, fromDate, toDate accept e.g. '20251' or '2025Q1' (these are QUARTERS, not calendar dates). Example: companyId 'SE-VOLV-B', parameterCode 'REV', fromDate '2024Q1', toDate '2025Q4'. Every row keeps its companyId and parameterCode; 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'.
`count`	No	false (default) skips totalCount for cheaper bulk paging.
`toDate`	No	Inclusive upper quarter bound, e.g. '20254' or '2025Q4'.
`fromDate`	No	Inclusive lower quarter bound, e.g. '20241' or '2024Q1'.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`companyId`	No	Company id from bolagsanalys_list_companies, e.g. 'SE-VOLV-B'. Omit to fetch ALL companies for the parameter/quarter (enables one-call ranking/aggregation).
`quarterId`	No	Single packed quarter, e.g. '20251' or '2025Q1'.
`parameterCode`	No	Parameter code from bolagsanalys_find_parameter; omit for all parameters.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Quarterly figures, one row per company+parameter+quarter.
`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 / figure / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / figure / type
```
Added value: +[
+  "number",
+  "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 / text / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / text / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv1.1.5Aug 7, 2026

TDQS

A4.1/5.0

Behavior3/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 — never writes.' It adds a useful behavioral detail ('every row keeps its companyId and parameterCode') and clarifies quarter values are packed quarters, not calendar dates. No contradiction with annotations; with readOnlyHint already present, the added behavioral disclosure is adequate but not extensive.

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 well-structured: purpose, optional narrowing, parameter provenance, quarter-format warning, and an example. Minor redundancy ('optionally' repeated; read-only stated twice), but every sentence earns its place and the key clarification is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description doesn't need to detail return values. It explains parameter origin, quarter-format pitfalls, and the all-companies behavior (omitting companyId for ranking/aggregation). It could mention pagination more explicitly, but the parameter descriptions cover that.

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 coverage is 100% with good field descriptions, so the baseline is 3. The description adds meaningful above-schema semantics: the quarter format ('2025Q1' vs '20251') with an explicit warning that these are quarters not dates, the provenance of companyId and parameterCode, and a full example. This justifies a 4.

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?

States a specific verb ('Fetch quarterly figures') and a clear resource ('Bolagsanalys data'), distinguishing it from sibling tools like bolagsanalys_search_data. Also names the companion tools that supply valid IDs, so an agent knows exactly what this tool does and how it fits.

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?

Gives clear usage context: pass companyId from bolagsanalys_list_companies, optionally narrow by parameterCode from bolagsanalys_find_parameter Joseph and quarter range. It does not explicitly state when not to use it versus bolagsanalys_search_data, but the flow is strongly implied by cross-tool provenance.

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

Deploy Server