Skip to main content
Glama

Dilisense Check Individual

dilisense_check_individual
Read-onlyIdempotent

Screen a person against sanctions/PEP/criminal watchlists (AML/KYC). Returns matching watchlist records with source type, PEP level, citizenship and sanction details. Example: dilisense_check_individual({ names: "Vladimir Putin", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "Vladimir Putin",
      "_apiKey": "your-dilisense-api-key"
    },
    "name": "dilisense_check_individual"
  }
}

Input Schema

NameRequiredDescriptionDefault
dobNoOptional date of birth to narrow matches, e.g. "1952-10-07"
fuzzyNoEnable fuzzy/approximate name matching (default true). Set false for exact matching only.
namesYesFull name of the individual to screen, e.g. "Vladimir Putin"
genderNoOptional gender filter: "male" or "female"
_apiKeyYesdilisense API key (free at dilisense.com, 100 calls/month)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"dilisense API key (free at dilisense.com — 100 calls/month)"New value: +"dilisense API key (free at dilisense.com, 100 calls/month)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value on top by describing the return payload: matching watchlist records with source type, PEP level, citizenship and sanction details. It does not cover rate limits or no-match behavior, but the schema already notes the 100 calls/month free tier.

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?

Three short sentences, front-loaded with the purpose and followed by the return shape and an example call. The example slightly duplicates the schema's built-in examples, but it usefully shows the minimal required-key call shape, so it largely earns its place.

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

Completeness4/5

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

For a five-parameter screening tool with no output schema, the description states the purpose, the domain, and what the response contains, which is sufficient for an agent to call it correctly. Missing only minor operational details such as handling of zero matches and whether results are paginated or capped.

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 every parameter including dob, fuzzy, gender and _apiKey is already documented in the schema. The description's example call illustrates usage but adds no semantic detail beyond what the schema states. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Screen a person against sanctions/PEP/criminal watchlists (AML/KYC).' That is enough to distinguish it from a generic name check, and 'a person' hints at the individual-vs-entity split. It does not explicitly name dilisense_check_entity or dilisense_check_name as the alternatives, so the sibling differentiation is only implied.

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?

The AML/KYC framing implies the compliance-screening context in which this tool belongs, which is useful. However, there is no explicit when-to-use versus when-to-use-a-sibling statement and no stated exclusions (for example, use the entity variant for companies). The agent must infer the routing.

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.