lore-mcp

search_corpora

Search across corpus manifests (JSONL files) for entries matching a query, with optional filtering by corpus IDs.

Instructions

Search across corpus manifests (JSONL files)

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": {
      "query": "<query>"
    },
    "name": "search_corpora"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`corpus_ids`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.8.5May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / corpus_ids / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / corpus_ids / default
```
Added value: +null
```

removedInput schema / properties / corpus_ids / description

Removed value: -"Specific corpus IDs to search (optional)"

removedInput schema / properties / corpus_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / corpus_ids / type
```
Removed value: -"array"
```
removedInput schema / properties / query / description
```
Removed value: -"Search query"
```

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?

With no annotations, the description fails to disclose behavioral traits such as return format, pagination, side effects, or any rate limits. The minimal description does not add value beyond naming the resource.

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 very short (one phrase). While concise, it sacrifices necessary detail. It front-loads the key info but lacks structure for a search tool.

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 presence of an output schema, the description does not clarify what the search returns (e.g., matches, scores, metadata). For a search tool, this omission leaves the agent uncertain about expected results.

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 does not elaborate on the parameters 'query' or 'corpus_ids'. Their meanings, formats, and constraints are left entirely to the agent to infer from the schema types.

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 (search) and the resource (corpus manifests in JSONL files). It distinguishes from sibling tools like search_local and search_transcripts by specifying the target data type.

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. It does not mention when not to use it or provide context about its suitability for different scenarios.

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