get, list.
The live tool list is authoritative: the company’s plan and your role can narrow this contract. Understand access.
When to use
Useinvoices_read for get, list, request_approval. Use invoices 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 of the company’s invoices including its current reviewed-content version and totals.
list
list
List this company’s local invoice summaries with settlement balances. Follow next_cursor while has_more; keep filters unchanged. The invoice record holds the legal registration and PDF.
request_approval
request_approval
Read the draft preview and return Emitir/Cambiar actions for authenticated web review. Present the preview and approval URL when the person prefers reviewing in Melso. This action does not issue the invoice; the owner’s external OAuth connection can issue its exact version with issue.
Output
list and get return invoices with their totals and status. request_approval returns the saved preview and the signed-in page where the owner issues the exact version.
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
Get the approval page for that draft
2
Read it again later to see whether it was issued