code402

Address Snapshot & Operator Policy Comparison

sanctions_address_screen

Read-onlyIdempotent

Exact EVM-address comparison against the identified address snapshot and existing operator block policy. Current legal status is unknown; is_sanctioned is null. valid=false preserves a local block; valid=null never authorizes a transaction. Names are not screened. Missing, stale or incomplete evidence is explicit; no UN/EU coverage or sanctions clearance is provided.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`subject`	Yes	EVM address (0x...) or ISO 3166-1 country code / jurisdiction name

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	Yes
`scope`	No
`valid`	Yes
`reason`	No
`subject`	No
`match_type`	No
`is_sanctioned`	Yes
`blocklist_match`	Yes
`snapshot_sha256`	No
`snapshot_status`	No
`sanction_program`	No
`screening_status`	Yes
`current_legal_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 17, 2026
RemovedOct 15, 2026

Changed9 schema fields changedOct 9, 2026

addedOutput schema / properties / blocklist_match

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / current_legal_status
```
Added value: +{
+  "type": "string"
+}
```
changedOutput schema / properties / is_sanctioned / type
```
Previous value: -"boolean"New value: +"null"
```

changedOutput schema / properties / sanction_program / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / screening_status
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / snapshot_sha256
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / snapshot_status
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / valid / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

changedOutput schema / required

Previous value: -[
-  "tool",
-  "valid",
-  "is_sanctioned"
-]New value: +[
+  "tool",
+  "valid",
+  "is_sanctioned",
+  "blocklist_match",
+  "current_legal_status",
+  "screening_status"
+]

AddedSep 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, yet the description adds genuine context: 'Current legal status is unknown; is_sanctioned is null,' 'valid=false preserves a local block,' and 'valid=null never authorizes a transaction.' These are safety-critical behavioral caveats not derivable from annotations, though some overlap with what an output schema would convey.

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?

Dense but front-loaded with the core purpose, followed by limitations and value semantics. Every sentence carries information, though the compounded clauses make it slightly harder to parse than necessary.

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?

With an output schema present, return values need not be restated, and the rich annotations cover the safety profile. The description fills the remaining gap by disclosing what is not covered (names, UN/EU jurisdictions) and the meaning of ambiguous valid states.

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 coverage is 100% and the single parameter is fully documented in the schema, so baseline 3 applies. The description adds no additional syntax, format, or constraint detail about the 'subject' parameter itself.

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 and resource: 'Exact EVM-address comparison against the identified address snapshot and existing operator block policy.' It also scopes itself against alternatives by declaring 'Names are not screened,' which separates it from name-based screening siblings.

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?

Usage boundaries are only implied through negative statements ('Names are not screened,' 'no UN/EU coverage or sanctions clearance is provided') rather than an explicit when-to-use or when-to-prefer-an-alternative rule. The valid=false/valid=null semantics hint at downstream behavior but do not frame tool selection.

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

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