Skip to main content
Glama

Dilisense Check Name

dilisense_check_name
Read-onlyIdempotent

Broad watchlist name check across all entity types, individuals, entities, vessels, aircraft. Returns all matching sanctions/PEP/criminal records plus the raw response. Example: dilisense_check_name({ names: "Kalibr", _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": "Kalibr",
      "_apiKey": "your-dilisense-api-key"
    },
    "name": "dilisense_check_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesName to screen, person, company, vessel or aircraft, e.g. "Kalibr"
_apiKeyYesdilisense API key (free at dilisense.com, 100 calls/month)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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)"
    • changedInput schema / properties / names / description
      Previous value: -"Name to screen — person, company, vessel or aircraft, e.g. \"Kalibr\""New value: +"Name to screen, person, company, vessel or aircraft, e.g. \"Kalibr\""
  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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing what comes back — all matching sanctions/PEP/criminal records plus the raw response — which matters since no output schema exists. It does not repeat the call-quota context, but that is already carried by the schema's _apiKey description.

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 purpose and scope are front-loaded in the first clause, and the return-content note is a single compact sentence. The trailing example call duplicates the schema's own examples field, making it the one element that does not fully earn 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?

With only two simple parameters, rich annotations, and no output schema, the description supplies nearly everything an agent needs: scope, coverage of entity types, and the shape of results including the raw payload. Minor gaps remain around matching strictness and result volume, but nothing essential to correct invocation 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% and both parameters are documented there, so the baseline is 3. The invocation example in the description merely restates the schema's own examples object without adding syntax, formatting, or matching-behavior detail beyond what the schema provides.

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?

States a specific verb+resource ('watchlist name check') and enumerates the entity types covered (individuals, entities, vessels, aircraft), which implicitly frames it as the broad-scope option versus the narrower dilisense_check_entity and dilisense_check_individual siblings. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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 word 'Broad' and 'across all entity types' implies this is the general-purpose screener to reach for when the entity type is unknown or a comprehensive sweep is wanted. However, there is no explicit when-to-use guidance and no statement about when a narrower sibling tool would be preferable.

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.