@sedis/mcp

Official

by sedis-ab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Find a Bolagsanalys parameter

bolagsanalys_find_parameter

Read-only

Search financial parameters by name fragment or group to get the code, English name, group, and description needed for data retrieval.

Instructions

Read-only. Discover the right financial parameter by name fragment or group and return each parameter's code, English name, group and description. Use this to resolve the parameterCode you then pass to bolagsanalys_get_data (alongside a companyId from bolagsanalys_list_companies). Example: nameContains 'revenue', group 'Income statement'. 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. 'Income statement'.
`pageSize`	No	Rows per page (v2 default 50, max 500), e.g. 50.
`nameContains`	No	Case-insensitive parameter-name fragment, e.g. 'revenue'.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Matching Bolagsanalys parameters.
`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 / 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 / period / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / period / 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 and openWorldHint, and the description reinforces this with 'read-only' and 'never writes.' It adds useful behavioral context by stating the data is shared reference data and by showing a concrete usage example, going slightly beyond the annotation-only signal without contradicting it.

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 and front-loaded with the tool's purpose, followed by workflow, an example, and a safety note. The only minor redundancy is repeating 'read-only' and 'never writes' in the final sentence, but overall every sentence earns its place.

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 and complete input schema, the description supplies the missing context: how this tool fits into the broader Bolagsanalys workflow, what kind of data it operates on, and how to filter results. An agent has enough information to select and invoke this tool correctly without further inference.

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%, so the baseline is already strong. The description adds extra meaning by providing a concrete example combining `nameContains` and `group`, and by explaining how the result's `parameterCode` is consumed downstream, which helps an agent understand the parameter's role in a larger workflow.

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 identifies the tool as a read-only parameter discovery endpoint: it finds financial parameters by name fragment or group and returns their code, English name, group, and description. It also distinguishes itself from data-retrieval tools by noting its output feeds `bolagsanalys_get_data`.

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 explicit workflow guidance: use this tool to resolve `parameterCode` for `bolagsanalys_get_data`, with `companyId` coming from `bolagsanalys_list_companies`. It does not explicitly discuss when not to use search-related siblings, but the chaining context is clear and actionable.

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

Deploy Server