When to use
Usedocuments for save, upload. Use documents_read for the companion actions. The live tool list determines availability.
Input
Actions
The tool’s schema combines the fields of every action. Each action accepts only its own fields below; sendaction with them.
Write actions
These actions change data. The server lists them only with a plan that includes the tools.save
save
Keep a file as one of the company’s documents: one sent or built in the Melso chat (attachment_id), or one PUT through upload (upload_id).
upload
upload
Reserve the upload of a local PDF or image of at most 15 MB: PUT its exact bytes to upload_url with the returned headers, then call save with upload_id.
Output
upload returns an upload_id, the upload_url and headers for a PUT. save keeps the uploaded file with its type and details. Saving a document does not issue an invoice or file a return.
The result uses MCP content blocks; JSON payloads are encoded in text and may also appear in structuredContent. Check isError before reading a success payload. When the server declares an outputSchema, it is reproduced below. Check the action result and its declared fields before reporting success.