AI summaries
A draft of each meeting with summary, decisions, requirements and possible tasks, each point with its minute.
- Category: Meetings and productivity
- Status: Available
- Requirements: A transcribed recording; An active Router IA key in the company paying for the recording
- MCP tools (Read only):
ver_grabacion - MCP tools (Write or modify):
reintentar_procesamiento_grabacion
What can you do with it?
| Part | Content |
|---|---|
| Summary | A short paragraph |
| Decisions | What was decided, with its moment |
| Requirements | What was asked for, with its moment |
| Possible tasks | Work to do, with its moment |
When should you use it?
- To review a long meeting without listening again.
- To move what was agreed onto the board with agreements to tasks.
How does it work in ArduMaker?
- It is generated after transcription, with a language model through the company's Router IA key.
- It is written in the transcript's language and only with what was said; ambiguous items are left out.
- The meeting text is treated as data: what someone said in the call does not change what the model does.
- It is always a draft: it does not create tasks or approve decisions.
What actually changes?
- If the transcript is corrected, the summary becomes stale and is no longer shown as current.
- Requesting a retry generates it again with the current text.
Diagram
- Transcript: segments with their moment
- Language model: via the company's Router IA
- Draft: summary, decisions, requirements, tasks
Expected result
The recording detail shows the summary marked as a draft, with each point linked to the meeting moment.
Errors and troubleshooting
- No summary: not transcribed yet, the transcript changed, or the company has no AI key.
- A summary can be wrong: check it against the transcript at the cited minute.
MCP access
ver_grabacionreturns the current summary with decisions, requirements and possible tasks, each withstart_ms.reintentar_procesamiento_grabacionrequests it again (write).
Full reference for each tool: /mcp/docs.