Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_sanctions_fuzzy_screen

Screen names against a built-in sanctions seed list and a caller-supplied watchlist using fuzzy matching to flag potential compliance matches.

Instructions

[Compliance & Trust] Fuzzy-match a name against a built-in seed list plus a caller-supplied watchlist Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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": "caelara_compliance_sanctions_fuzzy_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName to screen
thresholdNoMatch threshold 0.5-1 (default 0.85)
watchlistNoExtra names to screen against

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and partially meets it by disclosing latency (p50 12 ms, p95 16 ms) and the backing endpoint, which signals a network call to an external service. However, it does not state that the operation is read-only, what permissions or auth the endpoint requires, or what the response looks like on a hit versus a miss.

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?

Compact and front-loaded: the domain tag, the action, and the data sources come first, followed by performance and endpoint detail. The benchmark timestamp and URL are arguably marginal, but they are short and useful for latency-sensitive routing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a screening tool with no output schema, the description should explain what a screening call returns (match score, matched entry, boolean). It supplies latency and endpoint context but leaves return semantics and match-result interpretation undefined, which is a meaningful gap for the highest-stakes tool in the compliance family.

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%, so the baseline is 3. The phrase "built-in seed list plus a caller-supplied watchlist" does clarify the role of the `watchlist` parameter, but the `threshold` parameter's meaning and the interaction between threshold and match results are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Fuzzy-match") and names the exact resource set: a name checked against a built-in seed list plus a caller-supplied watchlist. An agent can immediately tell this is sanctions/watchlist screening rather than a generic matcher, though it does not explicitly contrast itself with the compliance 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 is implied by the compliance framing and the required `name` argument, but there is no explicit statement of when to use this versus other compliance tools, no prerequisites, and no note on exclusions or when not to screen.

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

Deploy Server

Other Tools