evidence_upload
Uploads a local file as evidence in a single step: computes SHA-256, registers the record, and uploads bytes to S3. Provide a file path or base64 content, along with required IDs.
Instructions
Uploads a local file as evidence in one step: computes its SHA-256, registers the evidence record (custodyType INTERNAL = EAD stores the file), and uploads the bytes to S3 — no manual hashing or PUT needed. Internally this follows the required EAD sequence: create INTERNAL evidence → receive uploadFileUrl (presigned S3 URL) → PUT file bytes → return uploaded:true. Requires: case_file_create → caseFileId, evidence_group_create → evidenceGroupId. Provide EXACTLY ONE of filePath (absolute local path, stdio/local mode only) or contentBase64 (base64-encoded file content, ~10 MB max). Use evidence_upload when the file is on the local machine; use evidence_create when you already have the SHA-256 hash, need to inspect/use uploadFileUrl manually, or have a public fileUrl. After this tool succeeds, verify with evidence_get/evidence_list and only then call evidence_seal. If this tool fails before returning an evidence id, check evidence_list before retrying; if retrying manually, use evidence_create with a fresh UUID. Local files must be under 1 GiB.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Human-readable title for the evidence | |
| fileName | Yes | File name including extension | |
| filePath | No | Absolute local path to the file (stdio/local mode only). The tool will create evidence, receive uploadFileUrl, and PUT this file to it. | |
| caseFileId | Yes | UUID of the case file | |
| contentBase64 | No | Base64-encoded file content (~10 MB max). The tool will create evidence, receive uploadFileUrl, and PUT these bytes to it. | |
| evidenceGroupId | Yes | UUID of the evidence group |