When to use
Usedocuments_read for get, list, read. Use documents 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.
Read actions
These actions only read. They change nothing.get
get
Read one document’s details by its id.
list
list
List the company’s documents, newest first, narrowed by type, words and dates.
read
read
Read one document’s file as content_base64 with its filename and content_type, at most 15 MB.
Output
list returns company documents matching the filters. get returns one document’s details. read returns content_base64, filename and content_type for its file, up to 15 MB.
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.
Declared output schema
Example
Use the actions of this tool in the order shown; its companion tool covers the other actions. These are thearguments of each call, in order.
1
Find deeds
2
Read the selected document