Skip to main content
Glama
AIDataNordic

Nordic Financial MCP

by AIDataNordic
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_filings

Read-only

Retrieve company filings, press releases, and macroeconomic summaries for Nordic markets. Use natural language queries to find text excerpts from listed companies in Norway, Sweden, Denmark, and Finland.

Instructions

Search the Nordic financial database for company filings, press releases and macroeconomic summaries.

Use this as the primary tool for any question about Nordic listed companies, markets or macro conditions. Do not use to retrieve a full document — results are chunked text excerpts; use parse_pdf_to_text for the full original document. Do not use for Swedish company registration data — use get_company_info instead.

The database contains ~1 million vectors across four Nordic markets (NO/SE/DK/FI).

COMPANY FILINGS Annual reports (XBRL/ESEF) and quarterly reports from ~1 500 listed companies across Oslo Børs, Nasdaq Stockholm, Nasdaq Helsinki, Nasdaq Copenhagen and First North markets. Covers 2020–present. Strong coverage for NO and SE; growing coverage for DK and FI.

EXCHANGE ANNOUNCEMENTS & PRESS RELEASES Regulatory filings, exchange announcements and press releases from listed companies in NO, SE, DK and FI. Covers 2020–present.

MACROECONOMIC SUMMARIES Quarterly macro summaries covering key indicators per country: Norway (NO): policy rate, FX rates, CPI, house prices, credit growth, electricity price, salmon price, GDP components Sweden (SE): policy rate, house price index, household credit Denmark (DK): policy rate, house price index, household loans, electricity price Finland (FI): house price index, household debt-to-income ratio, electricity price Use report_type='macro_summary' and country='NO'/'SE'/'DK'/'FI' to filter. Use fiscal_year and a quarter reference in your query, e.g. "Norwegian housing market Q1 2024".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query, e.g. 'Equinor dividend 2024' or 'Norwegian housing market Q3'
tickerNoFilter by company ticker, e.g. 'EQNR', 'SALM', 'NDA'
fiscal_yearNoFilter by fiscal year, e.g. 2024. Use 0 for no filter
report_typeNoFilter by type: annual_report, quarterly_report, press_release, exchange_announcement, macro_summary
sectorNoFilter by sector, e.g. 'energy', 'financials', 'salmon'
countryNoFilter by country: NO, SE, DK, or FI
limitNoNumber of results to return (1–20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true; description adds that results are chunked text excerpts, not full documents, and notes database size. No contradictions with annotations, but could further detail result structure or pagination.

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?

Description is longer but well-structured with sections and bullet points. It is informative without verbosity; each part serves a purpose. Could be slightly tighter but the complexity justifies length.

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 existence of output schema, description covers domain, content types, exclusions, and filtering guidance thoroughly. Provides practical examples and business context for Nordic markets, making it complete for an agent to use.

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 has 100% coverage, so baseline is 3. Description adds value with example queries, enumeration of report_types, and specific macro usage instructions, going beyond schema descriptions.

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 clearly states the tool searches for company filings, press releases, and macroeconomic summaries in the Nordic financial database. It distinguishes itself from siblings by specifying when to use alternative tools (parse_pdf_to_text for full docs, get_company_info for Swedish registration).

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 advises it as the primary tool for Nordic queries and provides clear exclusions: not for full documents (use parse_pdf_to_text) and not for Swedish company registration (use get_company_info). Also gives specific filter guidance for macro summaries with report_type and country.

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/AIDataNordic/nordic_financial_mcp'

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