When to use
Usegestiones_read for document_get, get, kinds, list, request_approval. Use gestiones 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.document_get
document_get
Read a document linked to this case, including a professional draft or receipt, as content_base64 with filename and content_type. Decode the bytes unchanged. At most 15 MB; larger documents are read in the authenticated web app.
get
get
Read one case with its conversation, versions, pending information request and documents, including drafts and filing receipts.
kinds
kinds
List the kinds of case this company can open: what each is, its details_schema (JSON Schema for create), whether a member of the company approves a draft, and how it is paid: payment.mode plan (included when payment.covered) or service (a one-off price, payment.amount_cents in EUR cents, paid by the owner in the web app before it is sent).
list
list
List the company’s cases, newest first, with status, kind, deadlines, current and approved versions, filing reference and tax-service coverage.
request_approval
request_approval
Return the current case version and authenticated web page where a member of the company reviews and approves it. Share approval_url. No MCP action approves, files or pays a return.
Output
list returns cases and their status. get returns a case with its conversation, versions, information requests and documents. kinds returns available kinds and their details schemas. request_approval returns the current version and the owner’s approval link. document_get returns the file as base64. No action approves or files a case.
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
See what the company can ask for
2
Read the case and any question it has