D&B Finance Analytics

Single MCP entry point for D&B Finance Analytics. Send the user's complete request in `query`; the agent privately chooses and executes only the Finance Analytics, Risk Analytics, and UBO tools authorized for the authenticated user, then returns a formatted final answer. MANDATORY FORWARDING RULE: You MUST call this tool for EVERY user request related to companies, credit, risk, finance, portfolios, reports, applications, alerts, scores, aging, ownership, or any business data query. This ALSO applies to meta-questions about this connector's capabilities, available tools, or supported features — for example 'what can you do', 'what tools are available', 'list your capabilities', 'what does this connector support'. The agent maintains an authoritative, license-aware list of capabilities; you MUST NOT answer capability questions yourself from the tool description or server metadata. NEVER answer these requests yourself, NEVER ask the user for additional information (such as DUNS numbers, email addresses, amounts, or company names) before calling this tool — the agent handles all clarification internally. Even if the request appears incomplete, forward it as-is. IMPORTANT: Pass the user's original wording as-is — do NOT rephrase, summarize, or rewrite their request. Keywords like 'PDF', 'download', 'export', 'report', and 'application' control internal routing; dropping or paraphrasing them causes the wrong operation. FOLLOW-UP RULE: For follow-up replies, ALWAYS include brief context so the agent knows which tool to route to, even if conversation history is unavailable. SEARCH PAGINATION (MANDATORY): When the user asks for the next or previous page of company search results, you MUST combine the original search term with the pagination action in your query. Examples: if the user searched for 'walmart' and then says 'next', send 'next page of search results for walmart'. If the user searched for 'google' and says 'show me more', send 'next page of search results for google'. If the user says 'previous page', send 'previous page of search results for <original company>'. This ensures the agent can route to the correct tool and maintain search context across turns. OTHER PAGINATION: For non-search pagination (e.g. portfolio, aging), include the tool area: 'next page of portfolio results', 'next page of aging results'. Row selection examples: instead of just '2', send 'select company 2 from the search results' or 'select row 2 for the credit application'. Confirmation examples: instead of just 'yes', send 'yes, proceed with the credit application'. Do NOT send bare keywords like 'next', '2', or 'yes' without context. RESPONSE RENDERING RULE: The agent returns pre-formatted markdown (tables, headers, bold labels, bulleted lists, charts). You MUST present the response to the user exactly as returned — preserve all markdown tables, formatting, and structure. Do NOT flatten tables into plain text, summarize tabular data into prose, or strip markdown formatting. Display the agent's response verbatim. SEARCH RESULT DISPLAY RULE (HIGHEST PRIORITY): When the response contains a company search results table, you MUST display the table exactly as returned. Never auto-select or assume which entity is the correct match — always present ALL results to the user and wait for their explicit selection. Show pagination instructions (e.g., "Type 'next' for the next page") exactly as the agent provides them. Do not interpret or act on pagination commands yourself. For pagination follow-ups, follow the SEARCH PAGINATION rule above (include the original search term with the pagination action). For row selection follow-ups, include the search context (e.g., 'select company 2 from the search results for walmart').

FinanceAnalyticsAgent