lore-mcp

backfill_query_embeddings

Backfill missing query embeddings in retrieval_telemetry for records created before Phase 4a, processing rows in configurable batches and optionally building a HNSW index.

Instructions

Backfill query_embedding column in retrieval_telemetry for rows that predate Phase 4a. Processes rows in batches. Set build_index=true to also create the HNSW index after backfill.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "backfill_query_embeddings"
  }
}

Input Schema

Name	Required	Description	Default
`batch_size`	No
`limit`	No
`dry_run`	No
`build_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.8.5May 28, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / batch_size / default
```
Added value: +32
```
- removedInput schema / properties / batch_size / description
```
Removed value: -"Rows per batch (1–200, default 32)"
```
- removedInput schema / properties / batch_size / maximum
```
Removed value: -200
```
- removedInput schema / properties / batch_size / minimum
```
Removed value: -1
```
- addedInput schema / properties / build_index / default
```
Added value: +false
```
- removedInput schema / properties / build_index / description
```
Removed value: -"If true, CREATE INDEX CONCURRENTLY after backfill (default false)"
```
- addedInput schema / properties / dry_run / default
```
Added value: +false
```
- removedInput schema / properties / dry_run / description
```
Removed value: -"If true, compute but do not write (default false)"
```
- addedInput schema / properties / limit / default
```
Added value: +1000
```
- removedInput schema / properties / limit / description
```
Removed value: -"Max rows to process (1–10000, default 1000)"
```
- removedInput schema / properties / limit / maximum
```
Removed value: -10000
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / required
```
Removed value: -[]
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
```
Addedv0.8.2May 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses batch processing and the optional index building, but omits details like error handling, performance impact, or whether the operation is reversible.

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?

Three concise sentences, each providing unique information: purpose, batching, and the build_index option. No unnecessary words.

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?

Despite an output schema existing, the description does not mention what the tool returns (e.g., count of rows affected, success status). This is a significant gap. Also, batching mechanics (e.g., order, progress feedback) are vague.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only explains build_index. batch_size, limit, and dry_run are not elaborated, leaving the agent to infer their purpose from names alone. This is insufficient for a tool with 4 parameters.

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?

Description clearly states the specific action: backfilling the query_embedding column in retrieval_telemetry for rows predating Phase 4a. This distinguishes it from sibling tools like kb_backfill_embeddings.

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?

Description mentions batching and the build_index option for index creation. While not explicitly stating when not to use, the context (retroactive backfill) is clear. No alternatives are named, but the sibling context provides differentiation.

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