lore-mcp

investigation_add

Add an investigation entry to open or append to an operations investigation, structured with topic, title, content, and tags.

Instructions

Add an investigation entry (open or append to an ops investigation)

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": {
      "topic": "<topic>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "investigation_add"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes
`title`	Yes
`content`	Yes
`tags`	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
```

addedInput schema / properties / tags / anyOf

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

addedInput schema / properties / tags / default
```
Added value: +null
```
removedInput schema / properties / tags / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / tags / type
```
Removed value: -"array"
```

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.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'add an investigation entry (open or append)' without explaining what 'open' vs 'append' entails, whether it modifies existing data, or any side effects. Missing critical transparency for a mutation tool.

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 overly terse. It lacks necessary detail about modes and parameters, making it incomplete rather than efficiently written.

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?

With 0% schema descriptions and no annotations, the description is insufficient for a tool with 4 parameters and an output schema. It does not explain the two modes, return values, or how inputs relate to behavior, leaving significant gaps.

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%, but the description does not elaborate on the parameters (topic, title, content, tags). It only vaguely refers to 'investigation entry', failing to add meaning beyond the parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'add' and the resource 'investigation entry', and specifies two modes ('open or append'). It is distinct from sibling tools like investigation_list or investigation_delete_note, though it could clarify what 'ops investigation' means.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., journal_append, kb_add). It does not mention when not to use it or any prerequisites, leaving the agent to infer usage context.

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