NewKwLab Tools

screen_sanctions

Screen a person or company name against the US OFAC SDN sanctions list (bundled snapshot, fuzzy matching with a similarity threshold) and return any matches with list details. An empty result means no match in the snapshot, not a legal clearance.

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": {
      "name": "<name>"
    },
    "name": "screen_sanctions"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name to screen
`limit`	No	Max matches, 1-25 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and does meaningfully disclose behavior: the data is a bundled snapshot (implying staleness limits), matching is fuzzy via a similarity threshold (implying non-exact, exploratory results), and empty results are not definitive clearance. What's missing is any mention of the fixed threshold value or how match scores are surfaced.

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 waste: the first front-loads what the tool does and returns, the second delivers the critical caveat about interpreting empty results. No redundant restatement of the name or schema.

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 two-parameter read tool with no output schema, the description covers scope, matching approach, return content, and result interpretation. The only gap is the shape of returned match records, which is summarized only as 'list details'.

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% with both parameters documented, so the baseline is 3. The description adds only the fuzzy-matching context, which isn't a parameter, and neither name nor limit gains semantics beyond the schema's own descriptions.

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 (screen), resource (person or company name), and target (US OFAC SDN sanctions list), plus the return content (matches with list details). This is clearly distinguishable from the validate_* and lookup_* siblings, which cover different domains.

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?

The description gives clear context for interpreting results, notably that an empty result means no match in the snapshot rather than legal clearance, which steers how an agent should report outcomes. It stops short of naming alternatives or explicit when-not-to-use conditions, but the domain is sufficiently distinct that no sibling routing is needed.

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

All NewKwLab Tools 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.

Resources

Need Help?