Skip to main content
Glama

EximAgent

by ai.eximagent
OverviewDiscussionsAdmin

OFAC SDN name screen

exim__sanctions__check
Read-onlyIdempotent

Screens a company or person name against the OFAC SDN list (substring and alias match) and returns matches with program and aliases. Advisory only; covers the SDN list, not other sanctions lists.

Input Schema

NameRequiredDescriptionDefault
nameYesCompany or person name to screen against OFAC SDN list

Output Schema

NameRequiredDescriptionDefault
dataYes
statsNo
_debugNo
summaryYes
warningsNo
nextActionsYes
correlationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / --name
      Removed value: -{
-  "description": "Company or person name to screen against OFAC SDN list",
-  "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}\\x00]|\\x00[\\t\\n\\v\\f\\r\\x85\\p{Z}]+\\x00",
-  "type": "string"
-}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Company or person name to screen against OFAC SDN list",
+  "maxLength": 8000,
+  "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}\\x00]|\\x00[\\t\\n\\v\\f\\r\\x85\\p{Z}]+\\x00",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "--name"
-]New value: +[
+  "name"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "value0": {
+      "additionalProperties": false,
+      "properties": {
+        "aliases": {
+          "$ref": "#/$defs/value1"
+        },
+        "entNum": {
+          "type": "string"
+        },
+        "matchKind": {
+          "type": "string"
+        },
+        "primaryName": {
+          "type": "string"
+        },
+        "program": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sdnType": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "aliases",
+        "entNum",
+        "matchKind",
+        "primaryName",
+        "program",
+        "sdnType"
+      ],
+      "type": "object"
+    },
+    "value1": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value2": {
+      "anyOf": [
+        {
+          "items": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value3": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value4"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value4": {
+      "additionalProperties": false,
+      "properties": {
+        "command": {
+          "type": "string"
+        },
+        "cost": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "rationale": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "command",
+        "cost",
+        "label",
+        "rationale"
+      ],
+      "type": "object"
+    },
+    "value5": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value6": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value7"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value7": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "value8": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "additionalProperties": false,
+  "properties": {
+    "_debug": {
+      "$ref": "#/$defs/value8"
+    },
+    "correlationId": {
+      "type": "string"
+    },
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "context": {
+          "type": [
+            "null",
+            "boolean",
+            "number",
+            "string",
+            "array",
+            "object"
+          ]
+        },
+        "cursor": {
+          "type": "string"
+        },
+        "has_more": {
+          "type": "boolean"
+        },
+        "items": {
+          "anyOf": [
+            {
+              "items": {
+                "$ref": "#/$defs/value0"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "context",
+        "has_more",
+        "items"
+      ],
+      "type": "object"
+    },
+    "nextActions": {
+      "$ref": "#/$defs/value3"
+    },
+    "stats": {
+      "$ref": "#/$defs/value5"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "warnings": {
+      "$ref": "#/$defs/value6"
+    }
+  },
+  "required": [
+    "data",
+    "nextActions",
+    "summary"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the match technique (substring and alias match, which implies possible false positives that require human review) and the advisory-only status of results.

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 sentences, zero filler, with the core action and matching semantics front-loaded and the coverage caveat placed second where it is most useful. Every clause earns its place.

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?

An output schema exists, so return structure need not be explained; the description still briefly notes that matches carry program and aliases. Combined with the stated list limitation and advisory status, this is sufficient for a one-parameter screening call, though no guidance is given on handling ambiguous or partial matches.

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 the single parameter's schema description ('Company or person name to screen against OFAC SDN list') is essentially identical to the description text, so the description adds no syntax, format, or normalization guidance (e.g., how to pass aliases or legal suffixes). Baseline 3 applies.

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 (screens), a specific resource (company or person name), a specific target list (OFAC SDN), and even the matching method (substring and alias match). No sibling tool covers sanctions screening, so an agent can immediately tell this apart from entity-resolution tools like exim__company__resolve.

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?

Gives a clear scope boundary: 'Advisory only; covers the SDN list, not other sanctions lists,' which tells the agent not to treat a negative result as comprehensive clearance. It stops short of naming a fallback or alternative source for the other lists, but no sibling tool provides one, so the guidance is near-complete for the available toolset.

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

All EximAgent toolsInspect
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