anchain-data-mcp

Official

Overview Schema Source Related Servers Discussions Admin

fuzzy_search_global_sanctions

Search international sanctions databases using fuzzy text matching to identify matches despite name spelling variations. Covers global, national, and regional datasets.

Instructions

Perform fuzzy text matching across international sanctions databases for broader and more comprehensive coverage.

Args: q: Fuzzy search query (e.g. Kesklinna) dataset: Global sanctions dataset to search in (global, au, ca, ch, eu, gb, il, jp, un, za, zm). Default: global

Cost: 200 credits

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

Input Schema

Name	Required	Description	Default
`q`	Yes
`dataset`	No		global

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It reveals the fuzzy matching nature and 'Cost: 200 credits,' but does not mention read-only status, permissions, or potential side effects. For a search tool, this is adequate but not rich.

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?

The purpose is stated clearly in the first sentence, followed by a well-structured Args section and a cost note. No redundant or unnecessary information; every sentence earns its place.

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?

The tool is simple, and an output schema exists so return values need not be explained. The description covers purpose, parameters, and cost, but lacks explicit alternative guidance. It is sufficient for a search tool with these structured inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description compensates fully. It explains q with an example ('Kesklinna') and dataset with the complete list of allowed values and default, adding significant meaning beyond the schema's bare types and defaults.

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?

The description clearly states the tool performs 'fuzzy text matching across international sanctions databases' with 'broader and more comprehensive coverage.' This specific verb+resource combination distinguishes it from sibling tools like search_global_sanctions (likely exact) and fuzzy_search_ofac (OFAC-specific).

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 phrase 'broader and more comprehensive coverage' implies use when a broader fuzzy match is needed, but it does not explicitly name alternatives or state when not to use. It offers clear context without exclusions.

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