Agent Decision & Evidence Tools (MCP + x402)

Sanctions screening (EU, UN, UK)

screen_sanctions_eu

Read-only

Check a person or company against the official EU (Commission FSF), UN Security Council and UK (HM Treasury OFSI) sanctions lists. 12,000+ listed entities, 50,000+ name variants, re-indexed daily, fuzzy matching. Each hit states its list, programme, reference and the list date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`lists`	No
`country`	No
`threshold`	No

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`clear`	No
`error`	No
`query`	No
`source`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`matches`	No
`message`	No
`missing`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`sources`	No
`unknown`	No
`accepted`	No
`retryable`	No
`threshold`	No
`checked_at`	No
`disclaimer`	No
`error_code`	No
`extensions`	No
`match_count`	No
`status_code`	No
`did_you_mean`	No
`not_included`	No
`country_filter`	No
`list_generated`	No
`lists_screened`	No
`missing_checks`	No
`names_screened`	No
`partial_evidence`	No
`entities_screened`	No
`compliance_workflow`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed9 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / country / title
```
Removed value: -"Country"
```
removedInput schema / properties / lists / title
```
Removed value: -"Lists"
```
removedInput schema / properties / name / title
```
Removed value: -"Name"
```
addedInput schema / properties / threshold / maximum
```
Added value: +1
```
addedInput schema / properties / threshold / minimum
```
Added value: +0
```
removedInput schema / properties / threshold / title
```
Removed value: -"Threshold"
```

removedInput schema / title

Removed value: -"screen_sanctions_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "query",
+        "country_filter",
+        "lists_screened",
+        "clear",
+        "match_count",
+        "matches",
+        "checked_at",
+        "list_generated",
+        "entities_screened",
+        "names_screened",
+        "sources",
+        "not_included",
+        "source",
+        "threshold",
+        "disclaimer",
+        "compliance_workflow",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for screen_sanctions_eu. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "clear": {
+      "type": "boolean"
+    },
+    "compliance_workflow": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "country_filter": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "entities_screened": {
+      "type": "integer"
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "list_generated": {},
+    "lists_screened": {
+      "items": {},
+      "type": "array"
+    },
+    "match_count": {
+      "type": "integer"
+    },
+    "matches": {
+      "items": {},
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "names_screened": {
+      "type": "integer"
+    },
+    "not_included": {},
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "query": {
+      "type": "string"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "source": {},
+    "sources": {
+      "items": {},
+      "type": "array"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "threshold": {
+      "type": "number"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds concrete behavioral traits: data scale (12,000+ entities, 50,000+ variants), daily re-indexing, fuzzy matching, and the per-hit fields reported (list, programme, reference, date). This gives the agent meaningful expectations about matching behavior and output content.

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 dense sentences, with the core action front-loaded and supporting statistics packed efficiently. No filler or redundant phrasing, and every clause adds useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters and zero schema coverage, the description omits crucial parameter semantics, making the tool hard to invoke confidently. It does cover purpose and behavioral context, and the output schema presumably documents return values, but the parameter gap leaves the definition incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no detail about the four parameters (name, lists, country, threshold). Since the ambiguity of 'lists', 'country', and especially 'threshold' is left entirely unexplained, the description fails to compensate for the empty schema.

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 states a precise action ('Check a person or company') against an explicit resource (EU/UN/UK sanctions lists), naming the governing bodies (Commission FSF, UN Security Council, HM Treasury OFSI). This clearly distinguishes it from broader sibling tools like check_counterparty_eu by scoping it to sanctions screening.

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 description implies usage context: use this tool when you need to screen a person or company against official sanctions lists. However, it provides no explicit when-not-to-use guidance or references to alternative sibling tools, leaving differentiation to inference.

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

All Agent Decision & Evidence Tools (MCP + x402) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Many tools are clearly separate (validate_vat, validate_iban, token_status, tx_status), but several overlap by combining the same core checks: check_counterparty_eu, must_verify_before_pay, tx_preflight, and invoice_to_pay_dossier_eu all screen sanctions and/or do VIES/IBAN checks. The descriptions help, but the boundaries between a KYB check, a payment gate, and a transaction preflight are subtle enough that agents can easily pick the wrong one.

Naming Consistency3/5

Names are uniformly lowercase snake_case, and patterns like validate_*, prepare_*, and *_eu give some predictability. However, the verb style is inconsistent: some tools are verb-led (read_url, screen_sanctions_eu, lookup_company_eu), others are noun-led (market_data, token_status, agentllm_micro), and paid/prepare pairs do not share a consistent naming scheme.

Tool Count3/5

24 tools is at the upper edge of what is reasonable, and the server mixes several unrelated concerns: EU VAT/invoice compliance, sanctions/KYB, US import readiness, AI disclosure/LLM inference, market data, URL reading, and transaction status. The core comply-to-pay workflow is well represented, but the extra domains make the tool list feel heavier and less like a single coherent service.

Completeness3/5

The EU invoice/payment compliance flow is fairly complete: e-invoice validation, VAT rules, VIES, IBAN, sanctions, transaction preflight, payment decisions, bookkeeping statements, and receipt verification are all covered. Obvious gaps remain for such a broadly named server: no export/other product compliance, no broader EU regulatory coverage, and the key invoice guard explicitly does not cover duplicate-ledger detection, internal approval, or delivery checks.

Sanctions screening (EU, UN, UK)

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources