Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_entity_kyb_composite

Screen legal entities for KYB compliance by checking sanctions fuzzy matches, VAT/EIN, IBAN/BIC, and disposable emails, then return a risk verdict.

Instructions

[Compliance & Trust] Entity KYB screen: sanctions fuzzy match + VAT/EIN + IBAN/BIC + email disposable check with risk verdict Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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": {
      "name": "<name>"
    },
    "name": "caelara_compliance_entity_kyb_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoBIC/SWIFT code
vatNoVAT number incl. country prefix, or US EIN
ibanNoIBAN
nameYesLegal entity name
emailNoContact email
watchlistNoOptional extra names to screen against

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it stays largely silent on behavior: it does not state that this is a read-only lookup (no side effects), whether it is billed or rate-limited, what permissions or API key are required, or how the "risk verdict" is graded. The measured p50/p95 latency and the endpoint host are genuinely useful operational details, but they do not cover the safety and auth profile an agent needs before invoking an unannotated 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?

The definition is a single front-loaded sentence that leads with the tag, then the operation and its component checks, followed by latency and endpoint metadata. It is dense but every clause carries information; the benchmark date and URL are the only slightly extraneous elements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must hint at return shape — it does so minimally by naming a "risk verdict", but never explains verdict levels, score ranges, or per-check result fields. Combined with the absence of annotations and any auth/rate-limit context, this is adequate but with clear gaps for a six-parameter composite screening tool.

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% — every one of the six properties has its own description (legal entity name, BIC/SWIFT, VAT incl. country prefix or US EIN, IBAN, contact email, optional extra watchlist names). The prose adds no syntax, format, or required-vs-optional guidance beyond that, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Entity KYB screen" names the resource and operation, and the description enumerates exactly which checks are bundled (sanctions fuzzy match, VAT/EIN, IBAN/BIC, disposable email) plus the risk verdict output. It never explicitly contrasts this composite with the single-purpose siblings (caelara_compliance_sanctions_fuzzy_screen, caelara_compliance_iban_bic_validator, etc.), so an agent must infer the composite-vs-single tradeoff from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Including the word "composite" and the bundle of checks implies this is the one-shot path when an agent wants a full entity screen rather than individual lookups. However, there is no explicit when-to-use / when-not statement, no mention of cost or rate limits relative to calling the cheaper single-check siblings, and no guidance on which optional fields to supply.

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

Deploy Server

Other Tools