Skip to main content
Glama

Corporate KYB & Compliance Risk Check

check_company_risk
Read-onlyIdempotent

Screen a company for KYB risk across BODACC insolvencies, EU sanctions, and French/EU public contract awards; returns a risk level and hit counts by category.

Instructions

Perform corporate KYB compliance screening across BODACC collective insolvencies, EU FSF sanctions, and French/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. '483680427'). Natural-person IDs are rejected per GDPR. Required if company_name is omitted.
company_nameNoRegistered corporate legal name (e.g. 'Lumiere Capital SAS'). 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. '483680427'). 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. 'Lumiere Capital SAS'). 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/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely useful behavioral context the annotations cannot: a $0.30 USDC/EURC per-call cost, DATAX_TOKEN dependency with an HTTP 402 failure mode, and the fact that results carry item_ref handles that cost $0.50 to unlock elsewhere.

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?

Four dense sentences, front-loaded with capability then cost then inputs then returns; no filler. Slightly parenthetical-heavy ('(returns HTTP 402 if unset)', "('dx_...')") but every clause carries actionable information.

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?

An output schema exists, yet the description still sketches the key return fields (risk_alert, risk_level values, hit counts, item_ref). Combined with payment mechanics, token dependency, and GDPR limits, an agent has everything needed to call this correctly and interpret the cost implications.

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%, so the schema already explains both parameters including the GDPR rejection and the either/or requirement. The description mainly restates that rule and adds only the 'supply both for broader matching' nuance, 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?

Names a specific verb and resource ('corporate KYB compliance screening') and enumerates the exact data sources screened (BODACC collective insolvencies, EU FSF sanctions, French/EU public contract awards). This is clearly distinguishable from siblings like find_distressed_auctions or get_tender_detail.

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?

States the input requirement ('Requires cif and/or company_name') and the key eligibility exclusion (personal national IDs blocked for GDPR), plus routes the agent to get_tender_detail for follow-up on hits. Lacks explicit when-not-to-use guidance versus the other search/discovery siblings, so not a full 5.

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