SONAR KYB

kyb_run_submit

Submits a full KYB due-diligence report asynchronously and returns a run_id for polling report status, enabling vendor, partner, and reseller risk checks.

Instructions

Submit a full KYB due-diligence report (async).

    Returns a run_id immediately. Poll with check_report_status after
    1-3 minutes. The report has everything kyb_findings returns plus a
    PASS / REVIEW / FLAG verdict per check, risk flags, a written
    summary and recommended next steps for a human reviewer.
    EUR 2.00 per call after the 3 free trial API calls.

    Args:
        company_name: Legal name of the company
        website: Company website URL, strongly recommended

Input Schema

Name	Required	Description	Default
`website`	No
`company_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), the description discloses the async contract, the 1-3 minute polling latency, and per-call billing — real behavioral traits the annotations do not carry. It doesn't say whether a failed run is charged or how long run_ids stay valid, which keeps it from a 5.

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?

Front-loads the action and the async/polling contract before listing args, and every sentence carries information. The docstring-style 'Args:' block is slightly redundant formatting but not wasteful.

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?

Even though an output schema exists, the description usefully previews the report contents (verdicts, risk flags, summary, next steps) and completes the async workflow picture with the polling step. An agent has everything needed to call it and handle the result correctly.

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 description coverage is 0%, so the description must compensate, and it does document both parameters: company_name as 'Legal name' and website as the URL, plus the useful qualifier 'strongly recommended' for a parameter that is optional with an empty-string default. Only minor format guidance (e.g., scheme/domain expectations) is missing.

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?

States a specific verb+resource ('Submit a full KYB due-diligence report') and immediately marks it async. It also distinguishes itself from the sibling kyb_findings by explaining the report contains 'everything kyb_findings returns plus' verdicts, so an agent can tell the two apart without opening either 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?

Explicitly routes follow-up behavior: 'Poll with check_report_status after 1-3 minutes', naming the alternative tool and the timing condition. It also discloses the pricing gate (EUR 2.00 per call after 3 free trial calls), which tells the agent when the call is costly to invoke.

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

This server cannot be deployed