Jithox EU Counterparty Sanctions Preflight

Screen an identifier

screen_sanctioned_identifier

Read-only

Deterministic EXACT match of an identifier (passport / national id / registration / other) against listed designations' identifiers — no fuzzy matching. 'match' / 'clear' / 'unavailable'. Screening evidence only; not a legal/compliance determination, not a clearance. A 'clear' is not a guarantee of non-designation — snapshot-scoped.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Optional identifier type (e.g. passport, national_id, registration).
`identifier`	No	The identifier value to check.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`billing`	Yes
`product`	Yes
`receipt`	Yes
`decision`	Yes
`retryable`	Yes
`capability`	Yes
`provenance`	Yes
`generatedAt`	Yes
`limitations`	Yes
`schemaVersion`	Yes
`receiptEnvelope`	No
`decisionCategory`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 31, 2026

addedOutput schema / properties / receiptEnvelope

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "algorithm": {
+      "type": "string"
+    },
+    "canonicalizationVersion": {
+      "type": "string"
+    },
+    "keyId": {
+      "type": "string"
+    },
+    "payload": {
+      "type": "object"
+    },
+    "publicKeyUrl": {
+      "type": "string"
+    },
+    "receiptVersion": {
+      "type": "string"
+    },
+    "resultHash": {
+      "type": "string"
+    },
+    "signature": {
+      "type": "string"
+    },
+    "verificationUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "receiptVersion",
+    "canonicalizationVersion",
+    "algorithm",
+    "keyId",
+    "payload",
+    "signature",
+    "publicKeyUrl",
+    "verificationUrl"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only and non-destructive annotations, the description discloses deterministic exact-match behavior (no fuzzy matching), possible outputs ('match'/'clear'/'unavailable'), snapshot-scoping, and the non-guarantee of a 'clear'. This is rich behavioral context that helps the agent set expectations.

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?

Two tight sentences deliver the core purpose, matching mode, output values, and key caveats. Every clause earns its place; no filler or redundancy.

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?

With a rich input schema, output schema, and clear annotations, the description still adds critical context: exact-match behavior, snapshot scope, evidentiary nature, and non-clearance status. It fully equips the agent to understand the tool's limits and role among siblings.

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?

The schema already documents both 'type' and 'identifier' with descriptions and 100% coverage. The description repeats the same identifier type examples from the schema, adding no new parameter-level meaning. Baseline 3 is appropriate when the schema shoulders the semantic load.

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 clearly states it screens an identifier (passport/national id/registration/other) against listed designations' identifiers using deterministic exact matching. This verb+resource definition distinguishes it from siblings like screen_sanctioned_name (which likely handles fuzzy name matching) and the listing/regime tools.

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

Usage Guidelines4/5

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

It explicitly notes this is screening evidence only, not a legal/compliance determination or clearance, and that a 'clear' is snapshot-scoped. This sets clear boundaries on use. It stops short of naming alternative tools, but the 'no fuzzy matching' clue implies when to use a different screening path.

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

All Jithox EU Counterparty Sanctions Preflight tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?