Skip to main content
Glama

Caelara Labs Compliance & Trust

sanctions_fuzzy_screen

Fuzzy-match a name against a built-in seed list plus a caller-supplied watchlist

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": "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 observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose one valuable trait — that matching runs against a built-in seed list rather than a live authoritative sanctions database, which signals coverage limits. However, it says nothing about what a match result contains, how scores are computed or reported, what happens below threshold, or whether results are case/normalization sensitive.

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?

A single well-formed sentence with the verb and both data sources front-loaded. Every clause carries information; there is no filler or redundancy.

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

Completeness2/5

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

With no output schema and no annotations, the description must explain what the tool returns and how to interpret results, and it does not — an agent cannot know whether it receives booleans, match scores, matched entity names, or ranked candidates. The absence of any note on the built-in list's limited scope or threshold-passing behavior leaves meaningful gaps for a screening tool.

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 all three parameters (name, threshold, watchlist) are already documented in structured form, establishing the baseline of 3. The description's phrase 'plus a caller-supplied watchlist' reinforces that the watchlist is additive to the built-in list, adding a small amount of meaning but no threshold or format detail beyond 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 states a specific verb and operation: 'Fuzzy-match a name' against two named sources (a built-in seed list and a caller-supplied watchlist). The resource and mechanism are unmistakable. It stops short of naming or contrasting any sibling, but the sibling set is a catalog of unrelated validators, so no confusion risk exists.

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 only implied: an agent can infer this is the screening tool to reach for when checking a name, but there is no explicit when-to-use statement, no exclusion criteria, and no guidance on when the caller-supplied watchlist path applies versus relying on the built-in list alone.

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