get_screening_info
Free: sanctions list versions, source hashes, freshness, entry counts, and the full per-tool price menu.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
sanctions-screening
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool is 'Free:' (no cost), and the listed outputs (versions, hashes, etc.) indicate a read-only, non-destructive behavior. With no annotations provided, the description adequately conveys the tool's behavioral profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently covers all key aspects of the tool's functionality without any redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description fully characterizes what the tool does and returns, leaving no ambiguity about its purpose or output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the description adds meaning by specifying exactly what the tool returns (versions, hashes, freshness, counts, prices), which goes beyond the empty schema to inform the user of the expected output.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool provides 'sanctions list versions, source hashes, freshness, entry counts, and the full per-tool price menu,' which is a specific verb+resource combination that clearly distinguishes it from sibling tools like screen_name or kyb_check.
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?
No explicit guidance on when to use or not use this tool is provided. However, its purpose as a free information retrieval tool is implied by the prefix 'Free:' and the listing of data it returns.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: screening names, crypto addresses, batches, PII scanning, jurisdiction checks, LEI resolution, API key creation, watch management, etc. Overlap between screen_name and screen_names_batch is intentional (single vs batch) and well-differentiated.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., screen_name, resolve_lei, check_jurisdiction). No mixing of conventions, making the set predictable and easy to navigate.
Tool Count5/5
With 13 tools, the server is well-scoped for its domain. Each tool addresses a specific need (screening, validation, LEI lookup, etc.) without unnecessary duplication or omission.
Completeness4/5
Covers most core workflows: name screening, batch, crypto, jurisdiction, LEI, PII scanning, validation, API key management, and watches. Minor gap: no explicit watch deletion or update tool, but watches are created with a max 90-day lifetime, so deletion may be intentional.