Skip to main content
Glama

UAI x402 Security Tools

sanctions-screen

Informational sanctions list lookup for agent pre-flight checks — matches names or Ethereum wallet addresses against a small curated subset of publicly designated OFAC SDN entries (~15). Not AML/KYC certified. Not a substitute for official OFAC search or licensed screening. (REST equivalent: POST /api/v1/sanctions-screen, $0.02)

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": {
      "query": "<query>"
    },
    "name": "sanctions-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPerson name, entity, or Ethereum wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral load. It does well on the things that matter most: severe coverage limits (~15 entries), a non-certified disclaimer, and a concrete invocation cost ($0.02 via POST /api/v1/sanctions-screen). However, it never describes the result shape — whether a call returns a boolean, a list of matched SDN entries, or partial-match scoring — and there is no output schema to fall back on, leaving the read semantics (narrow vs. fuzzy) undefined.

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?

Tight, front-loaded prose: capability and scope first, disclaimers second, operational details (REST path, price) last in a parenthetical. Every clause earns its place and none of it repeats structured fields.

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?

For a one-parameter, read-only lookup the description covers scope, honesty caveats, and cost, which is most of what an agent needs to decide and call. The one real hole is return-value behavior, which is unaddressed and uncompensated by an output schema, so a caller cannot predict what a hit looks like.

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 'query' parameter is fully documented in the schema, so the baseline is 3. The description restates the same accepted inputs ('names or Ethereum wallet addresses') without adding format guidance such as chain specificity, checksum casing, or how to express entity names — nothing beyond the 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?

States a specific verb+resource combination ('sanctions list lookup') and the exact matching surface ('names or Ethereum wallet addresses'), then bounds it to 'a small curated subset of publicly designated OFAC SDN entries (~15)'. It also distinguishes itself from adjacent things an agent might otherwise use ('official OFAC search', 'licensed screening'), so the purpose is unambiguous.

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 concrete use context ('agent pre-flight checks') and an explicit when-not ('Not AML/KYC certified. Not a substitute for official OFAC search or licensed screening'), which routes an agent toward authoritative sources for compliance-grade needs. It stops short of a crisp rule such as 'use for a quick sanity check only; escalate to official OFAC search when a hit occurs', so the alternative is named but the handoff condition is inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources