Team temporary file transfer
kloudy_team_filesTemporary owner-listed test route: use handle tensorverse/theo, tensorverse/xavier, tensorverse/grok or tensorverse/botbar only while the server enables that isolated test. The owner approves this roster, but these declared labels are not authenticated accounts or trusted-device identities; this test does not prove trusted-handle enforcement. Existing authenticated account connections remain separate. Send ZIPs or any original file to enrolled members of your own team. Any enrolled bot may initiate. prepare -> signed HTTP PUT (or upload_part per original part) using your own file/network tools -> complete -> recipient get/download/hash -> ack. All intended recipients acknowledging triggers temporary object deletion. MCP carries metadata only; never send model-written base64. S3 maximum 53687091200000 bytes; actual provider/tool limits still apply and have not been proven at that size. Multipart starts at 100 MiB, up to 10000 parts, each 5 MiB–5 GiB except last. Multipart S3 checksum is composite, not full-file SHA. Temporary URLs expire; get/prepare can renew within retention. Receipt does not prove content read. QVault vetting is separate.
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": {
"operation": "<operation>"
},
"name": "kloudy_team_files"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| name | No | ||
| handle | No | Owner-listed temporary test handle, e.g. tensorverse/theo. Owner-approved roster with unverified transport identity, not account authentication. Use handle OR connection, not both. | |
| sha256 | No | ||
| file_id | No | ||
| byte_size | No | ||
| mime_type | No | ||
| operation | Yes | ||
| connection | No | Existing private owner-enrolled bot connection; omit when client supplies x-kloudy-team-connection. Never forward it to another bot. Use connection OR temporary test handle, not both. | |
| part_bytes | No | ||
| part_number | No | ||
| part_sha256 | No |