Aurelmark

Get one current sanctions entry

sanctions_get_entry

Read-onlyIdempotent

Returns one current entry from the official US, UK, EU or Canada sanctions list (Canada entity-only; Australia pending, not loaded yet) by list and exact id, with proof of the official file it came from. Use it after sanctions_search_entries or sanctions_list_changes gave you an id; use sanctions_search_entries to match a name and sanctions_list_changes to see why an entry was removed. Inputs: list (required: ofac-sdn, ofac-consolidated, uk, eu, ca or au) and id (required, 1 to 40 letters/digits/._-, e.g. RUS0849 on uk or 36 on ofac-sdn). Output: entry with names, aliases, programmes, countries, first_seen and last_changed, and proof (official file URL, SHA-256, source date). An unknown or removed id returns the error entry_not_listed. Reads stored snapshots refreshed about every 6 hours; a monitoring feed, not a real-time clearance decision. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list": "<list>",
      "id": "<id>"
    },
    "name": "sanctions_get_entry"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The listing's id on that list, e.g. 36 or RUS0849
`list`	Yes	The list Allowed: ofac-sdn, ofac-consolidated, uk, eu, ca, au; e.g. ofac-sdn.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / list / description

Previous value: -"The list Allowed: ofac-sdn, ofac-consolidated, uk, eu; e.g. ofac-sdn."New value: +"The list Allowed: ofac-sdn, ofac-consolidated, uk, eu, ca, au; e.g. ofac-sdn."

changedInput schema / properties / list / enum

Previous value: -[
-  "ofac-sdn",
-  "ofac-consolidated",
-  "uk",
-  "eu"
-]New value: +[
+  "ofac-sdn",
+  "ofac-consolidated",
+  "uk",
+  "eu",
+  "ca",
+  "au"
+]

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), it discloses snapshot freshness (~6 hour refresh), that it is a monitoring feed not a clearance decision, the specific not-found error entry_not_listed, and the coverage caveats that Canada is entity-only and Australia is not loaded. It also spells out free-tier limits and what the payment-failure error contains, so failure modes are predictable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is strong and front-loaded: purpose, then usage, inputs, output, errors, freshness, caveats. However, the closing metering and pricing block is long and largely orthogonal to selecting or invoking this tool, which dilutes an otherwise tight definition.

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 no output schema, the description carries the return-value burden and does so by naming the entry fields (names, aliases, programmes, countries, first_seen, last_changed) and the provenance block (URL, SHA-256, source date). Combined with required-parameter detail, error behavior, and coverage caveats, an agent has everything needed to call it and interpret the result.

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%, so the baseline is 3; the description earns more by clarifying that the id is per-list ("exact id") and giving worked pairs such as RUS0849 on uk versus 36 on ofac-sdn, which explains why the same identifier is not portable across lists. It does not add format or casing rules beyond the schema pattern.

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?

Opens with a specific verb and resource: "Returns one current entry" from a named set of official sanctions lists, keyed by list and exact id. It also names the two sibling tools it is not (sanctions_search_entries, sanctions_list_changes), so the agent can separate the lookup tools without opening schemas.

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?

Gives an explicit when-to-use rule ("Use it after sanctions_search_entries or sanctions_list_changes gave you an id") and routes the alternatives by task: match a name versus see why an entry was removed. Exclusions and precedence are stated rather than implied.

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

All Aurelmark 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.