Fuzzy entity resolution and dedupe for names, addresses, and company records — the "is this the same person/company" problem that breaks exact-match joins. Clean CRM exports, merge duplicates, reconcile vendor lists. Pay-per-call via x402 (USDC on Base): $0.008/call, no account or API key. tools/list and /openapi.json are free for discovery.
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The purpose is singular and unambiguous.
A single tool named 'resolve' follows a clear verb pattern. With only one name, there is no inconsistency to evaluate.
One tool is borderline thin for a server, but it serves a focused, single-purpose domain (entity resolution). It feels minimal yet arguably appropriate for the narrow scope.
The tool fully covers the domain of entity resolution by accepting records, deduplicating, and returning merged canonical clusters. No additional operations appear necessary for the stated purpose.
Fuzzy-dedupe a list of records into clusters of likely-duplicate entities. Blocks by normalized token prefix, scores with Jaro-Winkler + token-set matching (exact on email/phone), unions matches above threshold, and returns a merged canonical record per cluster with a confidence score. Deterministic, no LLM calls.
| Name | Required | Description | Default |
|---|---|---|---|
| options | No | ||
| records | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully carries the burden of disclosure. It details the algorithm (blocking, scoring, matching) and states determinism and no LLM calls. However, it omits performance characteristics and error behavior, which prevents a perfect score.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise at two sentences, with the purpose front-loaded. Every sentence provides essential information about the tool's function and behavior without unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and 0% schema description coverage, the description provides algorithm transparency but insufficient parameter semantics and no usage guidance. It is reasonably complete for a deduplication tool but could add more context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must add meaning. It explains the 'threshold' parameter implicitly and the algorithm for matching, but does not detail the 'keys' parameter or the expected format of 'records'. This partially compensates but leaves gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Fuzzy-dedupe' and the resource 'list of records', explicitly describing the tool's function: deduplicating records into clusters. With no sibling tools, no further differentiation is needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus alternatives, but the lack of sibling tools reduces the need. The description implies its use for deduplication tasks, but does not provide conditions, prerequisites, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
resolve
Add one secure layer between your agents and this server.
