lore-mcp

deduplicate_results

Removes duplicate search results by comparing text similarity, using a configurable threshold to keep only unique entries.

Instructions

Remove duplicate search results based on text similarity

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": {
      "results": "<results>"
    },
    "name": "deduplicate_results"
  }
}

Input Schema

Name	Required	Description	Default
`results`	Yes
`threshold`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.8.5May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / results / description
```
Removed value: -"Array of search result objects"
```
addedInput schema / properties / results / items / additionalProperties
```
Added value: +true
```
addedInput schema / properties / threshold / default
```
Added value: +0.9
```

removedInput schema / properties / threshold / description

Removed value: -"Similarity threshold (0-1, default: 0.9)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv0.7.0May 25, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic functionality but does not disclose side effects, whether the input array is modified, or what the return value looks like. The output schema exists but is not leveraged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence, which is concise but arguably too brief. It front-loads the purpose but lacks necessary detail, making it minimally viable but not well rounded.

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?

Given the absence of annotations and low schema coverage, the description is incomplete. It does not explain the output schema, how the tool handles edge cases (empty results, threshold 0 or 1), or its relation to sibling tools like cluster_results or search_corpora.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the schema. It does not explain what 'threshold' represents (e.g., similarity threshold) or how 'results' should be structured. The parameter 'threshold' has a default but no explanation, leaving the agent uninformed.

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 action ('Remove duplicate'), the resource ('search results'), and the method ('based on text similarity'), distinguishing it from the sibling cluster_results which groups results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no prerequisites or exclusions provided. The description is too minimal to help an agent decide when to invoke deduplicate_results.

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