Skip to main content
Glama

kyb_run_submit

Order a full written KYB due-diligence report asynchronously. Returns a run_id to poll for per-check PASS/REVIEW/FLAG verdicts, risk flags, a written summary and reviewer next steps.

Instructions

Order a full written KYB due-diligence report (async). Use ONLY when the user asks for a full or written report: it costs EUR 6.00 per call (a new account's first call is free). For a quick check use company_lookup (EUR 0.01) or kyb_findings (EUR 0.50).

    Returns a run_id immediately; poll 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 next steps for a human reviewer.

    Args:
        company_name: Legal name of the company
        website: Company website URL, strongly recommended
        country: ISO 3166-1 alpha-2 country of registration; without it
            no company register is searched
        registration_number: The register's company number; needs country
        state: US only: 2-letter state of formation
        vat_number: VAT number with its country prefix
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>"
    },
    "name": "kyb_run_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
countryNo
websiteNo
vat_numberNo
company_nameYes
registration_numberNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / country
      Added value: +{
      +  "default": "",
      +  "title": "Country",
      +  "type": "string"
      +}
    • addedInput schema / properties / registration_number
      Added value: +{
      +  "default": "",
      +  "title": "Registration Number",
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "default": "",
      +  "title": "State",
      +  "type": "string"
      +}
    • addedInput schema / properties / vat_number
      Added value: +{
      +  "default": "",
      +  "title": "Vat Number",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover readOnly=false, openWorld=true, destructive=false; the description adds the commercially critical traits – EUR 6.00 per call, first call free on a new account, asynchronous execution returning a run_id, and expected latency. Those are behaviors the agent cannot recover from structured fields.

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 purpose, cost, and alternatives before the argument list, and every section earns its place. Minor redundancy in restating 'full/written report' twice, but nothing is genuinely wasted.

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?

Covers cost, async lifecycle, polling timing, returned identifier, and the report's contents (verdicts, risk flags, summary, next steps) – everything needed for a paid, long-running call. An output schema exists, so return-field detail is rightly summarized rather than enumerated.

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 description coverage is 0%, so the description carries the full burden and does: country gates register search, registration_number requires country, state is US-only and 2-letter, vat_number needs its country prefix, website is strongly recommended. This is exactly the dependency and format information the schema lacks.

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 action and artifact ('Order a full written KYB due-diligence report (async)') and immediately separates itself from company_lookup and kyb_findings by cost and depth. An agent can pick this tool over its siblings without opening any 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?

Gives an explicit use-only-when rule ('ONLY when the user asks for a full or written report') and names three alternatives with their prices so the agent can trade off cost versus depth. It also explains the follow-up path: poll check_report_status after 1-3 minutes.

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