Skip to main content
Glama
AIDataNordic

Nordic Financial MCP

due_diligence_report

Read-only

Run multiple targeted searches for due diligence, returning company-specific financial metrics, risk factors, sector context, and peer comparisons, with results grouped by section.

Instructions

Run multiple targeted searches and return results grouped by section for due diligence.

The agent defines all sections and queries — this tool does not decide what is relevant. Before calling, reason about which topics and data sources matter for this specific company: financial metrics, risk factors, sector-specific macro drivers (e.g. freight rates for shipping, power prices for aluminium smelters), recent press releases, peer context, etc. Formulate one query per section.

Each query is run independently as a full hybrid search (dense + sparse + rerank).

IMPORTANT — use 'ticker' on company-specific sections to avoid false positives. Without a ticker filter, documents that merely mention the company (e.g. as a customer or competitor) can rank above actual filings from that company. Omit 'ticker' only for sections where cross-company results are intentional, such as sector macro context or peer comparisons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyYesCompany name to research, e.g. 'Equinor', 'Norsk Hydro', 'Aker BP'
sectionsYesList of section dicts. Each must have 'name' (str) and 'query' (str). Optional: 'ticker' (str, filters results to that company), 'limit' (int, default 5, max 10). Maximum 8 sections.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations provide readOnlyHint true and openWorldHint false. The description adds behavioral details: each query runs as hybrid search, ticker filter to avoid false positives, and constraints on sections and limits. No contradiction.

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 with clear paragraphs, but it is slightly verbose. Could be more concise while retaining all critical information.

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?

Given the tool's complexity and presence of an output schema, the description covers input semantics, constraints, and rationale. It does not need to explain output format due to output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. The description adds significant value beyond the schema: explains the structure of sections, the importance of ticker, and default limit. This helps the agent use parameters correctly.

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 states the tool's purpose: 'Run multiple targeted searches and return results grouped by section for due diligence.' It uses specific verbs and nouns, and distinguishes itself from siblings like search_filings and get_company_info.

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 explains when to use the tool (due diligence) and provides guidance on how to formulate queries and use tickers. However, it does not explicitly mention when not to use it or name alternative siblings.

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