D&B Finance Analytics

MCP Tool Specification: application_decisioning_tool Tool Purpose ------------ The `application_decisioning_tool` is designed to: - Create a new credit application for a specific DUNS number. - If the customer asks to approve a credit limit, trigger the application process to approve that limit. - Pull the latest, real-time business data for that DUNS for credit decisioning. - Run the configured rules and/or credit limit models created by the user in the portal. - Determine whether the requested credit amount can be approved, declined, or requires review. - Return a fully formatted decision summary that can be directly shared with clients. Trigger Condition ----------------- This tool should be called whenever a user asks something like: - “Create an application for DUNS XXXXXXXX for amount $Y.” - “Can I approve $25,000 for this DUNS?” - “Check if this DUNS qualifies for the requested amount.” - “Can I approve a $50K credit limit for Company X?” - “I am owed $100K by Company Y. Can I increase the credit limit to $200K?” Important: 1. DUNS number is mandatory. If the user does not provide it, the tool must ask for it. If the user provides a company name, call the query_portfolio tool to search by name, ask the user to select the correct company, and obtain the DUNS number from that selection. 2. If this tool fails or throws an exception, fail over to the portfolio tool: search the DUNS data and take the decision accordingly. Expected Tool Input (JSON) -------------------------- { "duns_number": "string (required)", "credit_limit": "number (optional, default = 0) — the requested amount / credit limit", "currency": "string (optional, default = USD)", "email": "string (required; the applicant contact email. If the user has not provided it, ask for it before calling)", "additional_form_values": "object (optional) — extra application form values keyed by field name" } Behavior & Validation --------------------- - Validate that duns_number is provided; otherwise, ask for it. - Validate that email is provided; otherwise, ask the user for it before calling this tool. - Handle missing fields gracefully: * If credit_limit is missing, proceed with an application creation and decision only if rules allow; otherwise ask for the amount. * If currency is missing, use policy currency when known; otherwise default to USD. - Always include the rule set name that produced the outcome (approved/declined/review). - Include a narrative explaining the “why” behind the decision (e.g., scores, risk band, rule conditions). - Ensure the response is returned in the exact formatted structure below, suitable for sharing with clients. Output Format (Human-Readable), skip the section if you not found any related data in response ------------------------------------- The tool must return the following structure (fill values from the decision engine response): Application Details: Use entityInfoLW and show the formatted details. Do not show any Id fields such as companyId, entityId, or created_by. Show entityNo, Business Name, City, Address, and other relevant info. Status: decisionReviewHistoryMap.decisionReasonsForm.applicationCurrentStatus Decision Summary: An automated decision resulted in a {Decision Status} outcome on {Decision Date}. {Data Source} was your source of business information to make this decision. Currency View Policy Currency ({CURRENCY_CODE}) Credit Terms Recommended (if applicable) Credit Limit: {CREDIT_LIMIT} ({CURRENCY_CODE}) Payment Terms: {TEXT or "Not Set"} Early Payment Discount: {TEXT or "Not Set"} Analyst Instructions: {Narrative explaining the decision, risk score context, and how the limit/terms were derived.} The recommended credit terms were based on the following: (Credit Limit Rule conditions and values are displayed in {CURRENCY_CODE}) Condition Value Application Decision Rule: {Rule Name} The following information was used to calculate the CLM: Expression: {CLM Expression/Formula block as text} Field Value Default Score {Default Score} D&B Maximum Credit Recommendation {Max Credit Recommendation} ({CURRENCY_CODE}) Use: decisionReviewHistoryMap.decisionReasonsForm.automatedDecisionReasons.andCriteriaList has rule condition to describe this in table format mention as below The "{Triggered Rule Name}" rule triggered this review because of the following conditions: (Rule conditions and values are displayed in {CURRENCY_CODE}) Condition: {Condition 1} Value: {Value 1} Condition: {Condition 2} Value: {Value 2} {...add as many as returned...} And the following conditions were not met: Condition: {Unmet Condition 1} Value: {Unmet Value 1} Condition: {Unmet Condition 2} Value: {Unmet Value 2} {...optional if any...} Additional Data Used (optional): - {Any other scores, risk flags, alerts, trend indicators} Example (Filled with Sample Values) ----------------------------------- Status: Approved Decision Summary: An automated decision resulted in an Approved outcome on 13/02/2026. D&B was your source of business information to make this decision. Currency View Policy Currency (GBP) Credit Terms Recommended Credit Limit: 49,602.11 (GBP) Payment Terms: Not Set Early Payment Discount: Not Set Analyst Instructions: This application has been approved and scored above 4.1 on a scale of 1 to 10 (10 = lowest risk). Its credit limit is assigned based on this score and the configured model. The requested amount falls within the recommended limit for this risk band. The recommended credit terms were based on the following: (Credit Limit Rule conditions and values are displayed in GBP) Condition Value Application Decision Rule: Approved Rule The following information was used to calculate the CLM: Expression: CASE WHEN (Default Score) BETWEEN 0.0 AND 2.0 THEN 0.0*(D&B Maximum Credit Recommendation) WHEN (Default Score) BETWEEN 2.1 AND 4.0 THEN 0.3*(D&B Maximum Credit Recommendation) WHEN (Default Score) BETWEEN 4.1 AND 6.0 THEN 0.8*(D&B Maximum Credit Recommendation) WHEN (Default Score) BETWEEN 6.1 AND 8.0 THEN 1.0*(D&B Maximum Credit Recommendation) WHEN (Default Score) BETWEEN 8.1 AND 10.0 THEN 1.25*(D&B Maximum Credit Recommendation) ELSE 0 END Field Value Default Score 7.5 D&B Maximum Credit Recommendation 49,602.11 (GBP) The "Default Approval Rule" rule triggered this review because of the following conditions: (Rule conditions and values are displayed in GBP) Condition: Default Score Is Greater Than 4.1 Value: 7.5 And the following conditions were not met: Condition: Bankruptcy & Insolvency - Y/N Open Is True Value: — Condition: Country or Region - D&B Is Not Equal To US|CA Value: US Condition: Out of Business Indicator Is True Value: False Additional Questions the Tool May Ask ------------------------------------- 1) What is the requested credit amount? (if not provided), Just mention if not provided then I will proceed with default 0 2) What currency should be used? (if the policy currency is unknown and no currency was specified), Just mention if not provided then I will proceed with default workspace currency 3) Do you want me to run the standard rules or a specific rule set? Notes for Implementers ---------------------- - Ensure deterministic formatting: field headers and section labels must match exactly for client sharing. - If converting currencies, show the policy currency values and, optionally, include a footnote with the original currency and rate/timestamp if your system supports it. - Include timestamps in ISO 8601 internally; render user-facing dates in DD/MM/YYYY unless a different locale is specified. - Log the rule set version and data source version used for auditability (not necessarily shown to the client unless requested).

application_decisioning_tool

Use this tool to identify a company by DUNS or company name. For DUNS queries it returns the best single match; for company-name queries it returns up to 10 matches with company details.

fa_search_tool

Use this tool to get family tree data for a given duns number. It can return the tree structure or a downloadable PDF file. If the DUNS is not a valid nine-digit number it returns an INVALID_DUNS error, and if it does not resolve to a real company it returns a NOT_FOUND error (these are distinct from the single-location / no-related-entities result for a valid company).

get_company_ownership_tree

Retrieves a detailed Dun & Bradstreet report for a single company identified by its D-U-N-S number. Use this for deep-dive requests on one company (detailed report, summary, or executive report). Inputs: `duns_number` (required); optional `entity_id`, `report_sections` to limit the report to specific sections, and `continue_report_pull` to proceed past out-of-business or stale-data warnings. Returns a ReportResponse object with: `summary` (a short human-readable status message), `trade_up_note` (optional; present when the report was traded up from a branch D-U-N-S to the headquarters D-U-N-S, containing both D-U-N-S numbers), and `json_data` (a JSON string of the full structured report data). For guidance on formatting the returned data into a company report, use the `company-report-summary` skill via `fa_read_skill`.

get_company_report

List the user's Finance Analytics folders, or list the entities stored inside a folder. Use operation LIST to list folders, or LIST_ENTITY with a folder name to list the entities in that folder. This is a read-only tool.

list_folders

Modify Finance Analytics folders and their contents. Supported write operations: CREATE, DELETE, RENAME, COPY, MOVE, REMOVE, ADD. Use this after the user has identified entities (e.g. via a portfolio query or search) and wants to organize them. To only list folders or folder contents, use the read-only `list_folders` tool instead. If the response contains a URL, present it as a clickable hyperlink.

manage_folder

Search, filter, aggregate, sort, and count companies (entities) in the user's Dun & Bradstreet Finance Analytics portfolio. Inputs: - query_type: 'search' to return matching rows, 'count' to return the number of matches, or 'aggregation' to compute grouped metrics. - credit_file_type: optional entity-type filter — one of ACCOUNT, DUNSRIGHT, APPLICATION, or SNAPSHOT. Access to ACCOUNT and APPLICATION entities is license-gated; the tool returns an error when the caller lacks the required license. - filters: a list of criteria, each with field_name (a schema field), expression, and values. Standard expressions (EQUAL, NOT_EQUAL, BETWEEN, NOT_BETWEEN, IN, GREATER_THAN, LESS_THAN, NULL, NOT_NULL, EXIST, NOT_EXIST, etc.) compare a single field against constant value(s). The SCRIPT expression evaluates an Elasticsearch Painless script — supplied as the single item in values and referencing fields by their schema names — for conditions that compare or compute across multiple fields. - fields_to_display: the schema fields to return for each row. - sort_by / sort_by_direction: the field and direction ('ascending' or 'descending') used to order results. - page_number / page_size: pagination controls (page_size has a maximum of 10). - aggregation_operations / group_by_fields: for the 'aggregation' query_type, the metrics to compute and the fields to group them by. Field names supplied in filters, fields_to_display, sort_by, and group_by_fields must match the tool input schema exactly. Returns a PortfolioResponse with: summary (a human-readable description of the result or count), markdown_table (a Markdown table of the results when applicable), and json_data (a JSON string of the results, typically for aggregations).

query_portfolio