Skip to main content
Glama

Corporate KYB & Compliance Risk Check

check_company_risk
Read-onlyIdempotent

Screen companies for KYB compliance against EU sanctions and Portuguese public contract awards, returning risk alerts, levels, and category hit counts.

Instructions

Perform corporate KYB compliance screening across EU FSF sanctions and Portal BASE / TED Portuguese 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. '515615021'). Natural-person IDs are rejected per GDPR. Required if company_name is omitted.
company_nameNoRegistered corporate legal name (e.g. 'XpertGo Lda'). 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. '515615021'). 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. 'XpertGo Lda'). 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/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the $0.30 USDC/EURC per-call cost, the DATAX_TOKEN payment requirement, the HTTP 402 failure mode when unset, and the GDPR block on natural-person IDs. These are material pre-invocation facts an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with purpose, then commercial/auth constraints, then return shape. Every clause carries operational information and nothing is repeated for padding.

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, token-gated screening tool the description covers inputs, cost, auth failure, the GDPR constraint, and the return shape, and it points to the sibling needed to resolve item_ref handles. With an output schema present, nothing essential is missing.

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 documents cif and company_name including the either/or requirement and the GDPR rejection. The description restates the 'and/or' rule and the corporate-ID restriction without adding format or syntax detail, so 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?

"Perform corporate KYB compliance screening across EU FSF sanctions and Portal BASE / TED Portuguese public contract awards" names a specific verb (screening) and precisely scoped data sources, which no sibling tool covers. An agent can tell this apart from search_tenders or get_tender_detail without opening a 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?

It establishes the compliance-screening context and names the downstream alternative get_tender_detail ($0.50) for unlocking item_ref handles, which is genuine routing guidance. It stops short of explicit when-to-use/when-not rules relative to the other discovery tools, so it is 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.