Skip to main content
Glama
sedis-ab

@sedis/mcp

Official
by sedis-ab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Bolagsanalys figures for many companies (batch)

bolagsanalys_search_data
Read-only

Fetch quarterly financial data for up to 50 companies in one call, filtering by parameter and quarter range. Ideal for targeted analysis of a specific subset without extra requests.

Instructions

Read-only. Fetch quarterly figures for a SPECIFIC SET of companies in one call by passing companyIds (up to 50, from bolagsanalys_list_companies), optionally narrowed to a parameterCode (from bolagsanalys_find_parameter) and a quarter range. Use this for a specific N-company subset — v2's GET has no companyIdIn, so to fetch ALL companies instead omit companyId on bolagsanalys_get_data. Quarter bounds use packed ids: quarterId, fromDate, toDate accept e.g. '20251' or '2025Q1' (QUARTERS, not calendar dates). The cap is 50 — more is rejected. Returns the same envelope as bolagsanalys_get_data; every row keeps its companyId and parameterCode; read-only — never writes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed result page (first page = 1), e.g. 1.
sortNoComma-separated sort fields; prefix '-' for descending, e.g. '-name'.
countNofalse (default) skips totalCount for cheaper bulk paging.
toDateNoInclusive upper quarter bound, e.g. '20254' or '2025Q4'.
fromDateNoInclusive lower quarter bound, e.g. '20241' or '2024Q1'.
pageSizeNoRows per page (v2 default 50, max 500), e.g. 50.
companyIdNoSingle company id; OR'd with companyIds.
quarterIdNoSingle packed quarter, e.g. '20251' or '2025Q1'.
companyIdsNoUp to 50 company ids (from bolagsanalys_list_companies) to fetch in one call; over 50 is rejected.
parameterCodeNoParameter code from bolagsanalys_find_parameter; omit for all parameters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesQuarterly figures, one row per company+parameter+quarter.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.6
    • 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"
+]
  2. First observedv1.1.5

TDQS

A4.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it warns quarter bounds are packed quarter ids, not calendar dates; discloses the 50 cap is rejected; and specifies the response envelope and that rows keep companyId and parameterCode. No contradiction with the read-only annotation.

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?

Four dense sentences, with read-only and purpose front-loaded; each sentence adds a distinct fact (scope, alternative route, quarter encoding, cap, return behavior). No 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?

For a 10-parameter batch tool, the description covers selection criteria, sourcing of identifiers, quarter encoding, hard cap, and return shape; pagination/sort are already documented in the schema and output schema exists. Everything an agent needs to invoke correctly is provided.

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 100% of parameters, so baseline is 3; description adds real value by sourcing companyIds from bolagsanalys_list_companies, parameterCode from bolagsanalys_find_parameter, and clarifying quarterId/fromDate/toDate use packed quarter ids such as '20251'/'2025Q1'. It does not repeat page/count semantics, but the schema already documents those.

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?

Description states precise verb-resource: 'Fetch quarterly figures for a SPECIFIC SET of companies in one call' with companyIds up to 50. It explicitly distinguishes from bolagsanalys_get_data by scope, so an agent can select correctly without relying on schema.

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?

Gives an explicit when-to-use rule ('Use this for a specific N-company subset') and names the alternative for all companies ('to fetch ALL companies instead omit companyId on bolagsanalys_get_data'). Also notes the 50 cap is rejected, preventing wasted calls.

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

Deploy Server

Other Tools