Skip to main content
Glama

Caelara Labs Compliance & Trust

entity_kyb_composite

Entity KYB screen: sanctions fuzzy match + VAT/EIN + IBAN/BIC + email disposable check with risk verdict

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": "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 observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly doesn't. It implies a read-only screening operation but never states that, nor does it say what happens when optional inputs like VAT, IBAN, or email are omitted (are those checks skipped or does the call fail), whether external/paid lookups are involved, or whether results are cached.

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?

A single front-loaded fragment with zero filler; every clause names a concrete check. The telegraphic, noun-phrase style ('+ VAT/EIN + IBAN/BIC +') is efficient but slightly terse for an agent parsing intent.

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

Completeness2/5

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

For a 6-parameter composite tool with no annotations and no output schema, one line is thin. The description never characterizes the 'risk verdict' it advertises, nor explains behavior when only the required name is supplied, leaving the agent to guess at result shape before committing to a multi-source screening call.

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 coverage is 100%, so the baseline is 3. The description adds modest meaning by mapping parameters to checks — notably that email drives a disposable-address check, which the schema only calls 'Contact email' — but it says nothing about the 'watchlist' parameter or the fact that only 'name' is required.

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?

The description names a specific resource and operation ('Entity KYB screen') and enumerates the four sub-checks it bundles: sanctions fuzzy match, VAT/EIN, IBAN/BIC, and email disposable check, ending in a 'risk verdict'. That makes the composite nature legible next to siblings like sanctions_fuzzy_screen and vat_ein_checkdigit, though it never explicitly contrasts itself with them.

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?

Usage is only implied: the word 'composite' plus the list of bundled checks suggests 'call this when you want all screens at once rather than the individual tools.' There is no explicit when-to-use, when-not-to-use, or named alternative despite several sibling tools that perform each check separately.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources