fairquery-sanctions-screener

Official

by fairquery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Show sanctions list cache freshness (free)

list_cache_status

Read-onlyIdempotent

Check whether OFAC, EU, UK and UN sanctions lists are cached, fresh, stale, or missing before screening, and see if the next screen_names run will reuse or re-download them.

Instructions

WHAT: Show, per list (OFAC_SDN, OFAC_CONS, EU, UK, UN), whether a parsed copy is cached in your Apify account, when it was downloaded from the official source, the source publication date, entry count, and whether the next screen_names run will reuse it or re-download it. WHEN TO USE: before a large or time-critical screen_names batch (to know whether lists load in ~2-5 s or 10-40 s), or to state in a report how current the screened lists were. WHEN NOT TO USE: to screen names (screen_names, paid) or to list covered sources and their URLs (list_sources, free, no token). Does not refresh the cache; the next screen_names run does that. BEHAVIOR: GET requests to the Apify API only (your user, the key-value store "fairquery-sanctions-list-cache", one small record per list); never writes. Typically <1 s; up to ~3 s when the Actor has not yet written per-list meta records and the cached lists themselves (~1.6 MB gzip in total) are read instead. COST: free; needs your APIFY_TOKEN (the cache lives in your account) but starts no Actor run and charges no event. RETURNS: one status object; lists[] in the order above plus fresh / stale / missing summaries and a next_run sentence; Errors: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_API_FAILED (retryable). PARAMETERS: maxAgeHours sets the freshness window used for fresh (default 6, the window screen_names runs use; the Actor never accepts more than 12). A list is fresh only if it was downloaded at most maxAgeHours ago and is non-empty; stale lists are never used for screening, they are re-downloaded. store_found=false means no screen_names run has cached anything in this account yet, so all five lists are missing. read_from says whether a small meta record or the cached list itself was read. EXAMPLE: {} -> {"store_found":true,"lists":[{"list":"OFAC_SDN","cached":true,"fresh":false,"fetched_at":"2026-10-17T19:15:36Z","age_hours":21.27,"published_at":"2026-10-15T16:34:34Z","entries":19457,...},...],"stale":["OFAC_SDN","OFAC_CONS","EU","UK","UN"],"next_run":"OFAC_SDN, ... would be re-downloaded ..."}

Input Schema

Name	Required	Description	Default
`maxAgeHours`	No	Optional number 0-12, default 6 (the freshness window screen_names uses). 0 reports every cached list as stale. Example: 6

Output Schema

Name	Required	Description
`fresh`	Yes
`lists`	Yes	Per list: list, cached, fresh, fetched_at, age_hours, published_at, source_last_modified, entries, bytes, read_from
`stale`	Yes
`missing`	Yes
`next_run`	Yes	What the next screen_names run will do with each list
`store_id`	Yes
`store_found`	Yes	false = no cache in this Apify account yet
`cache_max_age_hours`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Oct 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile; the description adds substantial context beyond them: GET-only calls to the Apify API, the exact key-value store name, 'never writes', typical latency (<1 s, up to ~3 s in a fallback path), the ~1.6 MB gzip read fallback, free-of-charge status, the APIFY_TOKEN requirement, and the specific error codes including which are retryable.

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?

Strongly front-loaded with WHAT/WHEN/WHEN NOT/BEHAVIOR/COST/RETURNS/PARAMETERS/EXAMPLE headings, so an agent can scan to the relevant section. It is verbose in places, and the long inline EXAMPLE return dump partly overlaps with the output schema, but nearly every sentence carries actionable 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?

For a single-parameter, free read tool with a full output schema, this covers everything needed: trigger conditions, cost, token requirement, failure modes, and the meaning of the freshness window. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents the 0-12 range and default of 6, so the baseline is met. The description adds genuine semantics beyond the schema: what 'fresh' means (downloaded within maxAgeHours AND non-empty), that stale lists are re-downloaded rather than screened, that maxAgeHours=0 marks everything stale, and what store_found and read_from indicate.

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?

States a specific verb (Show), a specific resource (sanctions list cache freshness), and enumerates the exact lists covered (OFAC_SDN, OFAC_CONS, EU, UK, UN). It explicitly distinguishes itself from both siblings, naming screen_names and list_sources as the tools this is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has explicit WHEN TO USE (before large/time-critical screen_names batches, or to document list currency in a report) and WHEN NOT TO USE (screening names, listing sources), naming the alternative tool for each case. It also clarifies that this tool does not refresh the cache.

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

Deploy Server