Skip to main content
Glama

Corporate KYB & Compliance Risk Check

check_company_risk
Read-onlyIdempotent

Screen companies for KYB compliance against EU FSF sanctions and Italian ANAC/TED public contract awards, returning risk alerts, risk level, and hit counts by category.

Instructions

Perform corporate KYB compliance screening across EU FSF sanctions and ANAC PVL / TED Italian 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. '06500530016'). Natural-person IDs are rejected per GDPR. Required if company_name is omitted.
company_nameNoRegistered corporate legal name (e.g. 'Acme Cloud SRL'). 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. '06500530016'). 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. 'Acme Cloud SRL'). 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 already declare read-only, idempotent, non-destructive, open-world behavior, and the description goes well beyond them: per-call cost ($0.30 USDC or EURC), the DATAX_TOKEN auth requirement with an explicit HTTP 402 failure mode, GDPR-driven rejection of personal IDs, and the shape of the risk result. That is exactly the payment/auth/cost context an agent needs before invoking a paid tool.

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 tight sentences, front-loaded with the screening scope, then cost/auth, then inputs, then outputs. Slight redundancy in enumerating return fields that the output schema already documents, but nothing is padded or vague.

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 two-parameter paid screening tool, everything material is present: dataset scope, pricing and auth failure mode, input constraints, and the risk_level enum values including the 'UNKNOWN' case. With an output schema available, further return-value detail is unnecessary.

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 baseline is 3. The description's parameter remarks ('corporate tax/VAT IDs only; personal national IDs are blocked', 'cif and/or company_name') largely restate what the schema properties already say, adding little new meaning about formats or matching behavior.

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 and resource ('Perform corporate KYB compliance screening') and scopes it to named datasets (EU FSF sanctions, ANAC PVL / TED Italian awards). An agent can immediately tell this is a sanctions/compliance lookup, distinct from siblings like search_tenders or find_distressed_auctions.

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 concrete preconditions (needs cif and/or company_name, corporate IDs only, personal national IDs blocked for GDPR) and points to get_tender_detail for unlocking item_ref handles. It stops short of an explicit 'use this instead of X when Y' routing statement against the search-oriented siblings, so it is clear context rather than full when/when-not guidance.

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