Skip to main content
Glama

Corporate KYB & Compliance Risk Check

check_company_risk
Read-onlyIdempotent

Screen companies for KYB compliance risk across BaFin and EU sanctions plus German/EU public contract awards using corporate tax, VAT, or registry IDs.

Instructions

Perform corporate KYB compliance screening across BaFin supervisory sanctions, EU FSF sanctions, and German/EU public contract awards. Costs $0.30 USDC or EURC per call via DATAX_TOKEN (returns HTTP 402 if unset). Requires cif and/or company_name (corporate tax/VAT IDs only; personal national IDs are blocked for GDPR). Returns risk_alert boolean, risk_level ('HIGH', 'LOW', or 'UNKNOWN'), hit counts by category, and item_ref handles ('dx_...') unlockable via get_tender_detail ($0.50).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_company_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
cifNoCorporate tax, VAT, or commercial registry identifier without spaces (e.g. 'DE352520844'). Natural-person IDs are rejected per GDPR. Required if company_name is omitted.
company_nameNoRegistered corporate legal name (e.g. 'Deutsche Bank AG'). Required if cif is omitted; supply both for broader matching.

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
change_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / cif / description
      Added value: +"Corporate tax, VAT, or commercial registry identifier without spaces (e.g. 'DE352520844'). Natural-person IDs are rejected per GDPR. Required if company_name is omitted."
    • addedInput schema / properties / company_name / description
      Added value: +"Registered corporate legal name (e.g. 'Deutsche Bank AG'). Required if cif is omitted; supply both for broader matching."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "change_token": {
      +      "type": "string"
      +    },
      +    "result": {
      +      "properties": {
      +        "data_version": {
      +          "type": "string"
      +        },
      +        "operation": {
      +          "type": "string"
      +        },
      +        "risk_alert": {
      +          "type": "boolean"
      +        },
      +        "risk_level": {
      +          "type": "string"
      +        },
      +        "signals": {
      +          "items": {
      +            "properties": {
      +              "ambito": {
      +                "description": "Geographic jurisdiction or region.",
      +                "type": "string"
      +              },
      +              "detail_locked": {
      +                "description": "Always true until unlocked with get_tender_detail.",
      +                "type": "boolean"
      +              },
      +              "fecha_pub": {
      +                "description": "Publication date in YYYYMMDD format.",
      +                "type": "string"
      +              },
      +              "importe_texto": {
      +                "description": "Formatted amount string when available.",
      +                "type": "string"
      +              },
      +              "item_ref": {
      +                "description": "Opaque encrypted record reference ('dx_...') for get_tender_detail.",
      +                "type": "string"
      +              },
      +              "notice_type": {
      +                "description": "Notice classification.",
      +                "type": "string"
      +              },
      +              "preview": {
      +                "description": "Redacted summary preview without PII or entity identifiers.",
      +                "type": "string"
      +              },
      +              "seccion": {
      +                "description": "Registry section code.",
      +                "type": "string"
      +              },
      +              "unlock_price_micros": {
      +                "description": "Unlock price in USD/EUR micros (500000 = 0.50).",
      +                "type": "integer"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "summary": {
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds exactly the context annotations cannot: per-call cost in USDC/EURC, the DATAX_TOKEN auth requirement with the HTTP 402 failure mode, and the GDPR block on personal national IDs. These are the operational facts an agent needs before spending money or hitting an error.

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?

Single dense block, front-loaded with purpose, then cost/auth, then inputs, then returns — no filler sentences. The final clause enumerating return fields is partly redundant given an output schema exists, which keeps it from a 5.

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?

For a paid, auth-gated screening tool, the description covers the cost, the token prerequisite and its failure mode, input constraints, and the meaning of the risk_level values including the 'UNKNOWN' case. Nothing needed to call it correctly is missing; the return-field summary is a bonus since an output schema is present.

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

Parameters3/5

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

Schema description coverage is 100%, and both parameter descriptions already state the either/or requirement and the GDPR rejection rule. The description restates 'cif and/or company_name' and the corporate-ID restriction without adding format, syntax, or matching-behavior detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb and resource ('Perform corporate KYB compliance screening') and names the exact data sources covered (BaFin sanctions, EU FSF sanctions, German/EU contract awards). This scope is unambiguously distinct from the tender-search and catalog siblings, so an agent can route without opening the schema.

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?

Gives clear preconditions for invocation (cif and/or company_name, corporate IDs only) and a workflow handoff — item_ref handles are unlockable via get_tender_detail. It stops short of stating when NOT to use it or naming a cheaper alternative for a narrow lookup, so it lands at clear-context-without-exclusions.

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