MCP 服务器

Senzing

com.senzing/mcp
数据与分析 开发者工具 公开且可连接 MCP 2025-11-25

此 MCP 可以做什么

Supports Senzing entity-resolution workflows through data mapping, validation scripts, SDK scaffolding, documentation search, sample data, and troubleshooting.

analyze_record
Get the Senzing JSON analyzer script to validate mapped data files client-side. REQUIRED: `workspace_dir` (writable directory, e.g. ~/sz-workspace) — the call WILL FAIL without it. The analyzer validates records against the Entity Specification, examines feature distribution, attribute coverage, and data quality. Returns a Python script (no dependencies) with instructions. No source data is sent to the server. Typical workspace_dir values: Linux `/tmp` or `~/sz-workspace`; macOS `~/sz-workspace`; sandboxed envs: explicit path under home (do NOT assume /tmp exists).
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['workspace_dir'], 'properties': {'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default: "current").'}, 'file_paths': {'type': ['array', 'null'], 'items': {'type': 'string'}, 'default': None, 'description': 'File paths to analyze (Senzing JSON or JSONL files).\nCommands will be generated for each path.'}, 'workspace_dir': {'type': 'string', 'description': 'REQUIRED: Workspace directory for the analyzer script and any\ngenerated reports. Must be a writable absolute or relative path that\nalready exists in your environment. Do NOT assume `/tmp` exists —\nsome environments (e.g. Kiro) do not provide it. Typical values:\nLinux: `/tmp` or `~/sz-workspace`; macOS: `~/sz-workspace`;\nKiro/sandboxed: an explicit path under `~`, e.g. `~/sz-workspace`.\n\nDeclared as a non-optional `String` (no `#[serde(default)]`) so it\nappears in the generated JSON `inputSchema` `required` array. The prose\nhas always said REQUIRED, but as an `Option` it was schema-optional, so\nschema-respecting clients omitted it and looped on the `needs_param`\nguidance. An empty string still deserializes; the handler catches that\nand returns the guidance as an `isError` result.'}}}
download_resource
Download workflow resources by name. Pass `filename` (string) or `filenames` (array); calling with neither returns the list of available resources (it does not fail). Available: sz_json_analyzer.py, sz_schema_generator.py, sz_verbatim_check.py, sz_routing_report.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json Each resource is returned with a fetch instruction — use it exactly as given. Supports batch via `filenames` array. If a previously-known fetch instruction stops working, call this tool again to obtain the current one.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'inline': {'type': ['boolean', 'null'], 'default': None, 'description': 'Returns resource content inline instead of URLs. ALWAYS try with inline=false (default) first — only set inline=true if the URL fetch fails. Inline responses consume more context tokens. Large resources come back in BOUNDED CHUNKS: a truncated response carries `truncated: true`, `next_offset` and `total_chars` — call again with `offset` = `next_offset` to continue. For the Entity Specification prefer `search_docs`: it serves the same document already split by section, which is cheaper than paging through 75 KB.'}, 'offset': {'type': ['integer', 'null'], 'format': 'uint', 'default': None, 'minimum': 0, 'description': 'Character offset into the resource for `inline=true` pagination. Pass the\n`next_offset` from a previous truncated response. Default 0.'}, 'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default: "current").'}, 'filename': {'type': ['string', 'null'], 'default': None, 'description': 'Resource filename to retrieve (e.g. "sz_json_analyzer.py",\n"senzing_entity_specification.md"). Ignored when `filenames` is provided.'}, 'filenames': {'type': ['array', 'null'], 'items': {'type': 'string'}, 'default': None, 'description': 'Multiple resource filenames to retrieve in a single call.\nTakes precedence over `filename` when provided.'}}}
explain_error_code
Explain a Senzing error code with causes and resolution steps. Accepts formats: SENZ0005, SENZ-0005, 0005, or just 5. Returns error class, common causes, and specific resolution guidance
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['error_code'], 'properties': {'version': {'type': 'string', 'default': 'current'}, 'error_code': {'type': 'string'}}}
find_examples
Find working SOURCE CODE examples from 53 indexed Senzing GitHub repositories. REQUIRED: either `query` (string, for search) or `repo` with `file_path` or `list_files=true` — the call WILL FAIL without one. Three modes: (1) Search: pass `query` to find examples across all repos, (2) File listing: pass `repo` + `list_files=true`, (3) File retrieval: pass `repo` + `file_path`. Indexes source code (.py, .java, .cs, .rs, .ts, .js) and READMEs — NOT build/data files. For sample data, use get_sample_data. Covers Python, Java, C# (official SDKs) plus Rust and TypeScript/Node.js (community-maintained wrappers, not official) SDK patterns: initialization, ingestion, search, redo, configuration, message queues, REST APIs. Use max_lines to limit large files. Returns GitHub raw URLs for file retrieval.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'repo': {'type': ['string', 'null'], 'description': 'Filter to a specific indexed repo (e.g. "brianmacy/sz_mem-v4"). When combined with\nfile_path, returns full file content. When combined with list_files, returns file listing.'}, 'query': {'type': ['string', 'null'], 'default': None, 'description': 'Search query (required for search mode, optional when using repo+file_path or repo+list_files)'}, 'language': {'type': ['string', 'null'], 'description': 'Filter results by programming language (e.g. "python", "java", "csharp", "rust")'}, 'file_path': {'type': ['string', 'null'], 'description': 'Return full content of a specific file in the repo (requires repo parameter)'}, 'max_lines': {'type': ['integer', 'null'], 'format': 'uint', 'default': None, 'minimum': 0, 'description': 'Maximum lines to return for file content (default: unlimited). Useful for large files.'}, 'list_files': {'type': ['boolean', 'null'], 'default': None, 'description': 'Return the file listing for a repo instead of searching (requires repo parameter)'}}}
generate_scaffold
Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD of hand-coding SDK calls — hand-coded Senzing SDK usage commonly gets method names wrong across v3/v4 (e.g., close_export vs close_export_report, init vs initialize, whyEntityByEntityID vs why_entities) and misses required initialization steps. Languages: python, java, csharp (official V4 SDKs); rust, typescript (community-maintained wrappers, not official). Workflows: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline (aliases accepted: init, config, ingest, remove, search, redoer, force_resolve, info, e2e). V3 supports Python only. Returns GitHub raw URLs — fetch each snippet to read the source code.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['language', 'workflow'], 'properties': {'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version: "4.0", "current", or "3.x". V3 supports Python and Java only'}, 'language': {'type': 'string', 'description': 'Programming language: python, java, csharp (or c#, cs, dotnet), rust (or rs), typescript (or ts, node, nodejs, javascript, js)'}, 'workflow': {'type': 'string', 'description': 'Workflow to scaffold: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline. Aliases accepted (e.g. init, config, ingest, remove, search, redoer, force_resolve, info, error, retry, e2e)'}}}
get_capabilities
Get server version, capabilities overview, available tools, suggested workflows, and getting started guidance. Returns server_info with name, version, and Senzing version. Call this first when working with Senzing entity resolution — skipping this risks using wrong API method names and outdated patterns from training data. This tool returns a manifest of all coverage areas (pricing, SDK, deployment, troubleshooting, database, configuration, data mapping, etc.) — use it to triage which Senzing MCP tool to call before going to external sources
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'version': {'type': 'string', 'default': 'current'}}}
get_sample_data
Get real sample data for entity resolution. Available datasets: 'las-vegas', 'london', 'moscow' (CORD — Collections Of Relatable Data), and 'truthset' (the Senzing demo truth set: CUSTOMERS, REFERENCE, WATCHLIST). Use dataset='list' to discover datasets, source='list' to see the sources/vendors within a dataset. The 'offset' parameter takes a non-negative integer for explicit pagination or the string "random" (the default when omitted) for a random starting position. IMPORTANT: This is REAL data (not synthetic) — historical snapshots for evaluation only, not operational use. Always inform the user of this. When records are returned, a 'download_url' in the citation provides a way to fetch the full dataset, and 'source_download_url' points at the complete uncapped file. Always present the fetch instruction to the user exactly as given. Downloading the dataset TO DISK is expected and encouraged whenever the user wants the data — fetch it with a shell command (curl/wget) to a file and work from that file. What you must NOT do is pull the dataset INTO THE CONVERSATION: never echo, cat, paste or summarise raw records back into context, because these files run to hundreds of thousands of records. The inline records above are a small preview of the data shape, not the delivery mechanism. (An earlier wording of this line said only 'Do NOT download it yourself', which was read as a blanket ban on fetching and left users downloading files by hand.) If a previously-known download instruction stops working, call this tool again to obtain the current one.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['dataset'], 'properties': {'limit': {'type': ['integer', 'null'], 'format': 'uint', 'default': None, 'minimum': 0}, 'offset': {'oneOf': [{'type': 'integer', 'minimum': 0, 'description': 'Explicit zero-based record offset for pagination.'}, {'const': 'random', 'description': 'Start at a pseudo-random offset (same as omitting the field).'}, {'type': 'null', 'description': 'Random start (same as omitting the field).'}], 'default': None, 'description': 'Record offset. Use a number for explicit pagination, or "random" for a random starting position. Omit for random.'}, 'source': {'type': ['string', 'null'], 'description': 'Filter by data source/vendor within a dataset (e.g., "equifax", "ppp_loans").\nOmit to see all sources. Use "list" to list available sources.'}, 'dataset': {'type': 'string', 'description': 'Dataset name (e.g., "las-vegas", "london", "moscow").\nUse "list" to discover available datasets and their sources.\n(Required: schema-respecting clients cannot omit it — pass "list" to discover.)'}}}
get_sdk_reference
Get authoritative Senzing SDK reference data: method signatures and argument types per language binding, flags, response schemas, and V3→V4 migration. Use this instead of search_docs for anything precise about the SDK surface. Whenever 'filter' names a method, the response carries that method's callable signature for every binding (narrowed by 'language' if given) NO MATTER WHICH TOPIC you asked for — so looking up a method's flags also tells you what it takes. Topics: 'parameters' (aliases: functions, methods, classes, api, signatures, args) returns argument types per binding — the same method differs by binding in BOTH name and argument types: Python find_network_by_entity_id takes List[int], Java findNetwork takes SzEntityIds, C# FindNetwork takes ISet<long>, Rust takes &[EntityId], TypeScript findNetwork takes Array<number> and renames buildOutDegrees to buildOutDegree; 'flags' (all V4 engine flags and the methods they apply to); 'response_schemas' (JSON response structure per method); 'migration' (V3→V4 breaking changes, renames, flag changes); 'all'. 'filter' accepts any spelling — 'get entity', 'get_entity', and 'getEntity' all resolve. Pass 'language' (python/java/csharp/rust/typescript) to narrow to your binding; cross-binding divergence warnings are still included so you never translate a call between bindings by mistake
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['topic'], 'properties': {'topic': {'enum': ['parameters', 'params', 'parameter', 'signatures', 'signature', 'arguments', 'args', 'functions', 'function', 'methods', 'method', 'classes', 'class', 'api', 'flags', 'response_schemas', 'response_schema', 'responses', 'migration', 'all'], 'type': 'string', 'description': 'Topic: "parameters" (aliases: functions, methods, classes, api,\nsignatures, args), "flags", "response_schemas", "migration", or "all".\n\nYou do not need "parameters" just to see a signature: any topic filtered\nby a method name returns that method\'s signature in `method_signatures`.'}, 'filter': {'type': ['string', 'null'], 'default': None, 'description': "Optional filter: method name, class name, module name, or flag name.\nAny spelling resolves — `get entity`, `get_entity`, and `getEntity` all\nreach the same method.\n\nExamples are backticked, not double-quoted, on purpose: downstream\nclients derive a property's valid-value set from the double-quoted\ntokens in this description, so quoting examples here would advertise\nthem as the only accepted filters."}, 'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default: "current")'}, 'language': {'type': ['string', 'null'], 'default': None, 'description': 'Language binding: "python", "java", "csharp", "rust", or "typescript".\nNarrows signatures to that binding; cross-binding divergence warnings\nare kept either way. Omit to compare every binding side by side.'}}}
mapping_workflow
Map source data to Senzing JSON through a guided 8-step workflow. Use this INSTEAD of hand-coding Senzing JSON. REQUIRED ARGUMENTS for action='start' — arguments, not files: `file_paths`, the source file name(s) exactly as the user gave them (a LABEL the server never opens, so pass it even when the file is not readable from here), AND `workspace_dir` inside the `data` object (e.g. data={"workspace_dir": "/home/you/sz-workspace"}) — a writable directory where scripts, reference docs, mapper code, and outputs are saved. Do NOT assume /tmp exists (some environments like Kiro do not provide it). The call needs both arguments present; it does NOT need the file to exist. NO READABLE FILE, NO SHELL — START ANYWAY. If the user only DESCRIBED their columns, or you have no shell to run the profiler, step 1 accepts a `profile_summary` you write yourself: field_count from their column list, record_count as they stated it or 0 (zero means 'not measured' and is expected — it is not fabrication). An unreadable source file is NOT a reason to hand-code a mapping instead. Actions: start, advance, back, status, reset. Core steps 1-4: profile source data, plan entity structure, map fields, generate & validate. Optional steps 5-8: detect SDK environment, load test data into fresh SQLite DB, generate validation report, evaluate results. STATE: Every response returns a 'state' JSON object. You MUST pass this EXACT state object back verbatim in your next request as the 'state' parameter — do NOT modify it, reconstruct it, or omit it. The state is opaque and managed by the server. If you have lost the state, call with action='start' instead. Common errors: (1) omitting state on advance — always include it, (2) reconstructing state from memory — always echo the exact JSON from the previous response, (3) omitting data on advance — each step requires specific data fields documented in the instructions, (4) omitting the file_paths or workspace_dir ARGUMENTS on start — the server needs the names, not a readable file. Why not hand-code: hand-coded mappings produce wrong attribute names (EMPLOYER_NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and miss required fields like RECORD_ID.
只读
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'data': {'default': None, 'description': 'Step-specific data (for "advance" action). Legacy untyped channel; prefer\n`payload` (typed) when your client can satisfy it.'}, 'state': {'default': None, 'description': 'Workflow state from previous response (required for all actions except "start").\nCRITICAL: Pass the EXACT \'state\' JSON object from the previous mapping_workflow\nresponse verbatim — do NOT reconstruct, modify, or omit any fields.\nIf you have lost the state, call with action=\'start\' instead.'}, 'action': {'enum': ['start', 'advance', 'back', 'status', 'reset', None], 'type': ['string', 'null'], 'default': None, 'description': 'Action to perform. ONLY these values are valid: start, advance, back, status, reset.'}, 'payload': {'type': 'object', 'oneOf': [{'type': 'object', 'title': 'advance from step 1 (profile_source_data)', 'required': ['profile_summary', 'for_step'], 'properties': {'for_step': {'const': 1}, 'capped_files': {'type': 'array', 'items': {'type': 'string'}}, 'workspace_dir': {'type': 'string'}, 'profile_summary': {'type': 'array', 'items': {'type': 'object', 'required': ['schema_name', 'record_count', 'field_count'], 'properties': {'field_count': {'type': 'integer', 'minimum': 0, 'description': 'Distinct fields/columns in this schema — countable from a pasted column list even when the file itself was never read.'}, 'schema_name': {'type': 'string', 'description': 'Name of the source schema/table (for one flat file, its base name).'}, 'record_count': {'type': 'integer', 'minimum': 0, 'description': "Records in this schema. Use the profiler's count when it ran. If you could NOT read the file (the user only listed columns, or you have no shell), use the count the user stated, else 0. Zero is a legitimate, expected value — it means 'not measured', it is not fabrication, and it does not degrade the mapping."}}, 'additionalProperties': False}, 'minItems': 1, 'description': "One entry per source schema (table) discovered. Writable from the user's own description of their data — a readable file is not required."}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 2 (plan_entity_structure) — master-slot shape (master-less plan ungeneratable; required/enum/minItems subset, no contains/if-then)', 'required': ['master_schemas', 'support_schemas', 'for_step'], 'properties': {'for_step': {'const': 2}, 'decisions': {'type': 'array'}, 'questions': {'type': 'array'}, 'master_schemas': {'type': 'array', 'items': {'type': 'object', 'required': ['schema_name', 'data_source', 'record_type', 'record_id_source'], 'properties': {'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'data_source': {'type': 'string', 'description': 'UPPERCASE data source code'}, 'field_count': {'type': 'integer'}, 'record_type': {'enum': ['PERSON', 'ORGANIZATION', 'VESSEL', 'AIRCRAFT']}, 'schema_name': {'type': 'string'}, 'record_id_source': {'type': 'string', 'description': 'field name of the stable natural key (PREFERRED), or RECORD_HASH only when no stable unique field exists'}}, 'additionalProperties': False}, 'minItems': 1, 'description': "The main/primary entities (disposition 'master'). At least one is required — the slot IS the master disposition, so NO `disposition` field here."}, 'support_schemas': {'type': 'array', 'items': {'type': 'object', 'required': ['schema_name', 'disposition'], 'properties': {'role': {'type': 'string'}, 'to_key': {'type': 'string'}, 'from_key': {'type': 'string'}, 'join_key': {'type': 'string'}, 'key_field': {'type': 'string'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'disposition': {'enum': ['lookup', 'relationship', 'child']}, 'field_count': {'type': 'integer'}, 'schema_name': {'type': 'string'}}, 'additionalProperties': False}, 'description': 'Lookups, relationships, and child schemas that fold into the masters.'}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 3 (map_fields)', 'required': ['schema_mappings', 'for_step'], 'properties': {'for_step': {'const': 3}, 'decisions': {'type': 'array'}, 'questions': {'type': 'array'}, 'schema_mappings': {'type': 'array', 'items': {'type': 'object', 'required': ['schema_name', 'field_mappings'], 'properties': {'schema_name': {'type': 'string'}, 'code_mappings': {'type': 'object'}, 'field_mappings': {'type': 'array', 'items': {'oneOf': [{'type': 'object', 'required': ['disposition', 'feature', 'attribute'], 'properties': {'ref': {'type': 'string'}, 'custom': {'type': 'boolean', 'description': 'set true to deliberately map to a CUSTOM attribute not in the default Senzing spec (your schema added it); declare it via custom_attributes. Omit/false for standard catalog attributes.'}, 'feature': {'type': 'string', 'description': 'feature family, e.g. NAME'}, 'attribute': {'type': 'string', 'description': 'attribute code, e.g. NAME_FULL'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'usage_type': {'type': ['string', 'null']}, 'disposition': {'const': 'feature'}, 'ref_citation': {'type': 'string'}, 'source_field': {'type': 'string'}}, 'additionalProperties': False}, {'type': 'object', 'required': ['disposition', 'source_field'], 'properties': {'ref': {'type': 'string'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'disposition': {'const': 'payload'}, 'ref_citation': {'type': 'string'}, 'source_field': {'type': 'string'}}, 'additionalProperties': False}, {'type': 'object', 'required': ['disposition', 'source_field'], 'properties': {'ref': {'type': 'string'}, 'reason': {'type': 'string'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'disposition': {'const': 'ignore'}, 'ref_citation': {'type': 'string'}, 'source_field': {'type': 'string'}}, 'additionalProperties': False}, {'type': 'object', 'required': ['disposition', 'derived_as'], 'properties': {'ref': {'type': 'string'}, 'role': {'type': 'string', 'description': 'for REL_POINTER'}, 'value': {'type': 'string'}, 'domain': {'type': 'string', 'description': 'for REL_ANCHOR/REL_POINTER'}, 'source': {'type': 'string'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'derived_as': {'enum': ['DATA_SOURCE', 'RECORD_ID', 'RECORD_TYPE', 'REL_ANCHOR', 'REL_POINTER'], 'type': 'string'}, 'disposition': {'const': 'derived'}, 'ref_citation': {'type': 'string'}, 'source_field': {'type': 'string'}, 'justification': {'type': 'string', 'description': 'provenance for a constant derived RECORD_TYPE (validator-enforced)'}}, 'additionalProperties': False}, {'type': 'object', 'required': ['disposition', 'source_field', 'expected_features'], 'properties': {'ref': {'type': 'string'}, 'confidence': {'type': 'number', 'maximum': 1.0, 'minimum': 0.0}, 'disposition': {'const': 'extract'}, 'ref_citation': {'type': 'string'}, 'source_field': {'type': 'string'}, 'extraction_notes': {'type': 'string'}, 'expected_features': {'type': 'array', 'items': {'type': 'string'}}}, 'additionalProperties': False}]}}, 'type_discriminator': {'type': 'object'}}}, 'minItems': 1}}}, {'type': 'object', 'title': 'advance from step 4 (generate_validate)', 'required': ['verdict', 'for_step'], 'properties': {'verdict': {'enum': ['approve', 'rework_mapping', 'rework_code'], 'type': 'string'}, 'for_step': {'const': 4}, 'output_path': {'type': 'string'}, 'records_output': {'type': 'integer', 'minimum': 0}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 5 (detect_environment)', 'required': ['decision', 'for_step'], 'properties': {'decision': {'enum': ['skip', 'test_load'], 'type': 'string'}, 'for_step': {'const': 5}, 'senzing_config': {'type': 'object'}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 6 (load_test_data)', 'required': ['records_loaded', 'for_step'], 'properties': {'for_step': {'const': 6}, 'load_errors': {'type': 'integer', 'minimum': 0}, 'records_loaded': {'type': 'integer', 'minimum': 0}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 7 (validation_report)', 'required': ['report_generated', 'for_step'], 'properties': {'for_step': {'const': 7}, 'report_path': {'type': 'string'}, 'report_generated': {'const': True}}, 'additionalProperties': False}, {'type': 'object', 'title': 'advance from step 8 (evaluate_results)', 'required': ['verdict', 'for_step'], 'properties': {'verdict': {'enum': ['approve', 'marginal', 'rework_mapping', 'rework_code'], 'type': 'string'}, 'for_step': {'const': 8}}, 'additionalProperties': False}], 'default': None, 'description': 'Typed step payload for the "advance" action (H16). A discriminated `oneOf`\nover each step\'s accepted shape — pick the branch whose `for_step` equals\nthe step number you are advancing FROM. When present it is merged over\n`data` (payload wins); when absent, behavior is identical to sending `data`.'}, 'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default: "current").'}, 'file_paths': {'type': ['array', 'null'], 'items': {'type': 'string'}, 'default': None, 'description': 'Source file paths (required for "start" action). Also accepted inside\n`data` — see `workspace_dir` for why both placements are honoured.'}, 'workspace_dir': {'type': ['string', 'null'], 'default': None, 'description': 'Writable output directory (required for "start" action). Historically\nthis lived ONLY inside `data` while `file_paths` lived ONLY at the top\nlevel, so the two arguments of a single call sat in different places.\nClients reliably put both in one place — either place — and the half\nthat landed in the "wrong" one was silently dropped, producing a\n"required" error for an argument that WAS sent and forcing a retry.\nBoth placements are now accepted for both arguments; top level wins\nwhen a value is present in both.'}}}
reporting_guide
Guided reporting and visualization for Senzing entity resolution results. Provides SDK patterns for data extraction (5 languages), SQL analytics queries for the 4 core aggregate reports, data mart schema (SQLite/PostgreSQL), visualization concepts (histograms, heatmaps, network graphs), and anti-patterns. Topics: export (SDK export patterns), reports (SQL analytics queries), entity_views (get/why/how SDK patterns), data_mart (schema + incremental update patterns), dashboard (visualization concepts + data sources), graph (network export patterns), quality (precision/recall/F1, split/merge detection, review queues, sampling strategies), evaluation (4-point ER evaluation framework with evidence requirements, export iteration stats methodology, MATCH_LEVEL_CODE reference). Returns decision trees when language/scale not specified.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['topic'], 'properties': {'scale': {'type': ['string', 'null'], 'default': None, 'description': 'Scale tier. Omit to get the scale decision tree.'}, 'topic': {'enum': ['export', 'extract', 'reports', 'report', 'aggregate', 'summary', 'analytics', 'entity_views', 'entity', 'get', 'why', 'how', 'compare', 'data_mart', 'datamart', 'mart', 'schema', 'database', 'dashboard', 'visualization', 'visualize', 'chart', 'charts', 'graph', 'network', 'relationships', 'quality', 'accuracy', 'precision', 'recall', 'f1', 'audit', 'splits', 'merges', 'truth', 'evaluation', 'eval', 'er_quality', 'validation', 'evaluate', 'assessment'], 'type': 'string', 'description': 'Topic: "export", "reports", "entity_views", "data_mart", "dashboard", "graph", "quality", "evaluation"'}, 'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default "current")'}, 'language': {'type': ['string', 'null'], 'default': None, 'description': 'Programming language. Omit to get the language decision tree.'}}}
sdk_guide
Install Senzing and scaffold SDK code across 5 platforms (linux_apt — Ubuntu/Debian via apt or apt-get, .deb packages; linux_yum — RHEL/CentOS/Fedora via yum/dnf/rpm; macos_arm — Homebrew/brew; windows — scoop or chocolatey/choco; docker) and 5 languages (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution — prefer this over hand-coding install commands or engine configuration. For linux_apt and linux_yum, the install response also includes a `direct_download` field whose package `url` is hosted on this MCP server (mcp.senzing.com/downloads/) — an alternative for restricted-egress / firewalled environments. Use each package's `url` exactly as returned. Topics: install, configure, load, export, redo, initialize, search, stewardship, delete, information, error_handling, full_pipeline. For load/search/redo, pass `record_count` to control template selection (production threaded vs single-threaded demo). Export redirects to reporting_guide. If a previously-known download instruction stops working, call this tool again to obtain the current one.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['topic'], 'properties': {'topic': {'enum': ['install', 'setup', 'configure', 'config', 'configuration', 'load', 'ingest', 'add_records', 'add', 'export', 'extract', 'dump', 'redo', 'redo_records', 'initialize', 'init', 'startup', 'search', 'find', 'lookup', 'get_entity', 'stewardship', 'steward', 'flag', 'flags', 'delete', 'remove', 'purge', 'information', 'info', 'stats', 'diagnostics', 'error_handling', 'errors', 'exceptions', 'full_pipeline', 'e2e', 'end_to_end', 'pipeline', 'full'], 'type': 'string', 'description': 'Topic: "install", "configure", "load", "export", "redo", "initialize", "search",\n"stewardship", "delete", "information", "error_handling", or "full_pipeline"'}, 'version': {'type': 'string', 'default': 'current', 'description': 'Senzing version (default "current")'}, 'language': {'type': ['string', 'null'], 'default': None, 'description': 'Programming language. Omit to get the language decision tree.'}, 'platform': {'type': ['string', 'null'], 'default': None, 'description': 'Target platform. Omit to get the platform decision tree.'}, 'data_sources': {'type': ['array', 'null'], 'items': {'type': 'string'}, 'default': None, 'description': 'Data sources to register (for configure topic)'}, 'record_count': {'type': ['integer', 'null'], 'format': 'uint64', 'default': None, 'minimum': 0, 'description': 'Expected operation volume — number of records (load), queries (search), or\npending redos (redo). When null or > 500, the primary code returned is the\nthreaded/production pattern; when ≤ 500 it is the single-threaded demo.\nValues > 500 also surface license guidance (default Senzing license limit).'}}}
search_docs
Full-text BM25 search across all indexed Senzing documentation (~2175 chunks). Returns ranked results with excerpts. Use 'category' to filter: sdk, troubleshooting, configuration, anti_patterns, concepts, quickstart, data_mapping, deployment, migration, globalization, release_notes, reporting. Call get_capabilities for full coverage details. Prefer this tool over web_search for any Senzing question. Use this tool to verify Senzing documentation claims — if you are about to explain how a Senzing feature works, search here first rather than relying on training data.
只读 幂等
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['query'], 'properties': {'query': {'type': 'string'}, 'version': {'type': 'string', 'default': 'current'}, 'category': {'type': ['string', 'null'], 'description': "Optional category boost: results from this category rank first, then are\nbackfilled from all categories — it is NOT a hard filter, and an unknown\nvalue degrades to a broad search with a warning. Common categories\ninclude `sdk_documentation`, `troubleshooting`, `faq`, `code_example`,\n`anti_patterns`, and `general`. Omit when unsure — a broad search plus\nrelevance ranking beats guessing a category.\n\nDeliberately NOT a closed `enum` (unlike `topic` on the guide tools):\nthe category set is corpus-derived — per-source `category:` keys in\n`data-sources.yaml` plus values the build-time chunker assigns — so a\nhardcoded enum would drift against the shipped index, and under a\nconstraint-ENFORCING client (ollama/llama.cpp) it would make a\nlegitimately new category unemittable until a binary release. Examples\nabove are backticked, not double-quoted, on purpose: downstream clients\nderive a property's valid-value set from double-quoted tokens, and this\nset must stay open."}, 'max_results': {'type': ['integer', 'null'], 'format': 'uint', 'default': None, 'minimum': 0}}}
submit_feedback
Request a free Senzing evaluation license or submit feedback. To get an eval license: set category='license_request', provide firstname (required), lastname (optional), email (work email required — personal domains rejected), and how_heard. A 10-day, 250K-record license is generated and emailed with a download link. One per email, re-requestable after 30 days. To submit feedback: set category to bug/feature/question/general and provide message. Show the user the exact message and get confirmation before sending.
可能执行破坏性操作 可访问外部资源
输入模式
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'properties': {'email': {'type': ['string', 'null'], 'default': None, 'description': 'Work email address (required for license_request — personal email domains not accepted)'}, 'message': {'type': ['string', 'null'], 'default': None, 'description': 'Feedback message (required for bug/feature/question/general)'}, 'category': {'type': ['string', 'null'], 'default': None, 'description': 'Category: bug, feature, question, general, or license_request'}, 'lastname': {'type': ['string', 'null'], 'default': None, 'description': 'Last name of the requester (optional for license_request)'}, 'firstname': {'type': ['string', 'null'], 'default': None, 'description': 'First name of the requester (required for license_request)'}, 'how_heard': {'type': ['string', 'null'], 'default': None, 'description': 'How the requester heard about Senzing (required for license_request)'}}}
已更改
find_examples
2026年10月1日 02:54
已更改
mapping_workflow
2026年9月25日 03:03
已更改
mapping_workflow
2026年9月23日 02:54
已更改
download_resource
2026年9月23日 02:54
已更改
get_sample_data
2026年9月21日 03:01
已添加
submit_feedback
2026年9月17日 12:37
已添加
search_docs
2026年9月17日 12:37
已添加
sdk_guide
2026年9月17日 12:37
已添加
reporting_guide
2026年9月17日 12:37
已添加
mapping_workflow
2026年9月17日 12:37
已添加
get_sdk_reference
2026年9月17日 12:37
已添加
get_sample_data
2026年9月17日 12:37
已添加
get_capabilities
2026年9月17日 12:37
已添加
generate_scaffold
2026年9月17日 12:37
已添加
find_examples
2026年9月17日 12:37
已添加
explain_error_code
2026年9月17日 12:37
已添加
download_resource
2026年9月17日 12:37
已添加
analyze_record
2026年9月17日 12:37