Skip to main content
Glama

Dilisense Check Entity

dilisense_check_entity
Read-onlyIdempotent

Screen a company against sanctions and watchlists (AML/KYC). Returns matching records with source type, jurisdiction and sanction details. Example: dilisense_check_entity({ names: "Gazprom", _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": "Gazprom",
      "_apiKey": "your-dilisense-api-key"
    },
    "name": "dilisense_check_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuzzyNoEnable fuzzy/approximate name matching (default true). Set false for exact matching only.
namesYesCompany/organization name to screen, e.g. "Gazprom"
_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 read-only, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuine value beyond that by stating what comes back (matching records with source type, jurisdiction and sanction details), which matters because there is no output schema.

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?

Two sentences of purpose plus a return summary, all front-loaded with no filler. The trailing example largely duplicates the schema's examples block, which is the only wasted text.

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 three-parameter lookup with no output schema, the definition covers purpose, result shape, and a worked call. It stops short of noting that an empty result means no match, which would help an agent interpret a null response.

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 all three parameters are documented in the schema, including the fuzzy default and the API-key call quota. The description's inline example repeats the schema's own examples field and adds no new parameter meaning, so the baseline 3 applies.

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?

"Screen a company against sanctions and watchlists (AML/KYC)" gives a specific verb (screen) and resource (company) plus the domain. The word "company" implicitly separates it from dilisense_check_individual and dilisense_check_name, but no sibling is named explicitly.

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 parenthetical implies the compliance-screening use case, but there is no explicit when-to-use guidance, no exclusions, and no pointer to the individual/name variants. An agent must infer the boundary itself.

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.