EAD Factory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

evidence_case_file_search

Read-onlyIdempotent

Searches case files with optional filters (name, status, dates, pagination). Use to find a caseFileId when you don't have it, or to list what exists before creating a new case file with evidence_case_file_create.

Instructions

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filter`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.4.0Sep 14, 2026

removedInput schema / properties / filter / properties / code / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / filter / properties / code / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedInput schema / properties / filter / properties / createdFrom / anyOf

Previous value: -[
-  {
-    "format": "date-time",
-    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / filter / properties / createdUntil / anyOf

Previous value: -[
-  {
-    "format": "date-time",
-    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / filter / properties / title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / filter / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / allOf

Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "_metadata": {
-        "additionalProperties": {},
-        "properties": {
-          "currentPage": {
-            "type": "number"
-          },
-          "pageSize": {
-            "type": "number"
-          },
-          "totalPages": {
-            "type": "number"
-          },
-          "totalRecords": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      "records": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "category": {
-              "type": "string"
-            },
-            "code": {
-              "type": "string"
-            },
-            "createdAt": {
-              "type": "string"
-            },
-            "id": {
-              "type": "string"
-            },
-            "metadata": {
-              "allOf": [
-                {
-                  "additionalProperties": {
-                    "type": "string"
-                  },
-                  "propertyNames": {
-                    "type": "string"
-                  },
-                  "type": "object"
-                },
-                {}
-              ]
-            },
-            "owner": {
-              "type": "string"
-            },
-            "status": {
-              "allOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "string"
-                }
-              ]
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "records": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "category": {
-              "type": "string"
-            },
-            "code": {
-              "type": "string"
-            },
-            "createdAt": {
-              "type": "string"
-            },
-            "id": {
-              "type": "string"
-            },
-            "metadata": {
-              "allOf": [
-                {
-                  "additionalProperties": {
-                    "type": "string"
-                  },
-                  "propertyNames": {
-                    "type": "string"
-                  },
-                  "type": "object"
-                },
-                {}
-              ]
-            },
-            "owner": {
-              "type": "string"
-            },
-            "status": {
-              "allOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "string"
-                }
-              ]
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "type": "object"
-  }
-]

addedOutput schema / properties / data / properties

Added value: +{
+  "_metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "currentPage": {
+        "type": "number"
+      },
+      "pageSize": {
+        "type": "number"
+      },
+      "totalPages": {
+        "type": "number"
+      },
+      "totalRecords": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "records": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "code": {
+          "type": "string"
+        },
+        "createdAt": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "metadata": {
+          "allOf": [
+            {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            {}
+          ]
+        },
+        "owner": {
+          "type": "string"
+        },
+        "status": {
+          "allOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / data / type
```
Added value: +"object"
```

First observedv1.3.1Aug 5, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description itself does not disclose any behavioral nuances beyond what the generic search verbs imply — no note on result scope, matching semantics, pagination behavior, or performance. It adds little value beyond the 'when-to-use' aspect and hence is lower than what would be expected to reach a 3.

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?

Two sentences: the first provides the action and a list, the second provides concrete usage context. No filler words, the information is front-loaded and each sentence has a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core decision when to use the tool is explained and an output schema exists, so the return type doesn't need to be restated. Yet the filter parameter is a nested object with many fields, and the description only gives a partial and slightly inaccurate list of filters. Thus, while sufficient to understand the tool's role, it falls short of fully guiding an agent through the filter structure.

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?

All schema descriptions are absent, so the description must compensate, but it only mentions 'name, status, dates, pagination'. It omits code, owner, category, metadata, and sort, and crucially calls 'title' as 'name'. This leads to potential confusion in an agent that relies on the description, so the compensation is partial and somewhat misaligned.

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 states the verb 'Searches' and the resource 'case files', and its use case of finding a caseFileId when absent. It also explicitly contrasts with evidence_case_file_create, which separates it from creation. However, it uses 'name' where the schema defines 'title', causing slight ambiguity in field recognition.

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?

The description clearly states when to use it: to find a caseFileId when you don't have it, or to list before creating with evidence_case_file_create. This provides useful context and names an alternative. It doesn't explicitly mention when to switch to evidence_case_file_get once the ID is known, so it is strong but not exhaustive.

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

Deploy Server