AllEars.Vet

Permanently delete one of the authenticated veterinarian's patients along with associated events, photos and consultation links. This is destructive and cannot be undone — always ask the user for explicit confirmation before calling. A patient that has any digitally signed receita CANNOT be deleted (the signed prescriptions are legal documents with retention duties); the tool returns `error: patient_has_signed_prescriptions` in that case. (Editing and deletion are enabled by default; if this tool is unavailable the user has switched them off in Settings → Integrações.)

delete_patient

Permanently delete one of the authenticated veterinarian's consultation sessions, including its transcription, summary, audio chunks and linked patient events. The patient and guardian records are kept. This is destructive and CANNOT be undone. NEVER use it to fix a consultation linked to the wrong patient — use `move_session` for that, which keeps everything. Requests like 'remover/tirar/desvincular a consulta do paciente X' are AMBIGUOUS: they usually mean re-linking, not destruction — ask which one the user wants and present `move_session` as the first option. Only call this tool when the user unambiguously asks for permanent deletion, and always with their explicit confirmation. (Editing and deletion are enabled by default; if this tool is unavailable the user has switched them off in Settings → Integrações.)

delete_session

Financial summary of one month (default: the current one): amount received (gross and net of card fees), split by payment method, what is still receivable and overdue (with the guardians who owe), AI-suggested charges waiting for confirmation, and — for members who can see the whole clinic — expenses paid and due soon, plus the commissions of the month per vet (what is owed, whether it was already posted as a bill and whether that bill was paid). Use it for any "quanto recebi / faturei / está em aberto / vencido / quanto temos de comissões a pagar" question. Amounts are integer cents in BRL; present them as R$ with two decimals.

finance_summary

List the vet's AllEars.Vet agenda between two dates: care tasks ("lembretes"), the vet's own calendar events ("compromissos", recurring occurrences expanded), patient/guardian birthdays, health-plan expiries and, when the vet connected Google Calendar, their Google events (source `google_event`, READ-ONLY — no tool can edit those; they live in the vet's Google account). Window of up to 93 days — prefer narrow windows ('esta semana', 'este mês'). Calendar-event rows carry `calendar_event_id` and `occurrence_date`; pass BOTH to update_calendar_event/delete_calendar_event when editing a recurring event. Care-task rows carry `care_task_id` for resolve/snooze/update_care_task. The result carries `now` (the vet's current instant): a row whose `starts_at` is before it ALREADY HAPPENED — never present it as an upcoming commitment.

list_calendar

List the authenticated veterinarian's care tasks ("lembretes": vaccine boosters, rechecks, deworming, protocol steps). Filter by bucket ('overdue', 'today', 'next7' / 'next30' = the next 7 or 30 days counting from TODAY (today included), 'month' = until the end of the CURRENT calendar month (NOT the next 30 days), 'resolved', 'all' = every open task whatever the date), by kind, or by patient. When unsure of the window the user means, prefer 'all' — it never misses a future task. Tasks come sorted by due date and include the patient, guardian contact and origin (consultation / protocol / manual).

list_care_tasks

List charges ("cobranças"): open, overdue, AI-suggested drafts, quotes ("orçamentos", proposals not yet accepted, so nothing is owed on them) or paid, optionally for one guardian or patient. Returns amounts in integer cents (BRL) and each charge id — the id is what record_payment needs. Use it to answer "o que o responsável X deve", "quais cobranças estão vencidas", or to find the charge before registering a payment or building its collection message (show_collection_message).

list_charges

List clinic documents (termos de consentimento, atestados, declarações, laudos, autorizações, recibos, …) for the authenticated veterinarian. NOT for prescriptions — receitas live in list_prescriptions. Optional filters by patient, kind, status ('draft', 'awaiting_signature', 'signed', 'superseded') and free-text search.

list_documents

List the practice's bills to pay ("despesas", "contas a pagar"): upcoming (unpaid, soonest first), overdue, or paid in a month; optionally only those due within N days or matching a text. Returns each expense id (what pay_expense needs), description, supplier, category, amount in integer cents (BRL), due and paid dates, and whether it is a commission bill. Only members with full finance access see expenses.

list_expenses

List the authenticated veterinarian's guardians (responsáveis — pet owners). Optional case-insensitive search across name, code, email, phone and linked patient names — multiple words narrow the match (e.g. 'maria amora' finds the Maria who owns Amora). Each guardian comes with the patients linked to them.

list_guardians

List the active members of the vet's clinic workspace (team) with their internal user id, name and role ('owner', 'vet' or 'staff'). Call it BEFORE assigning an agenda entry to a colleague — create_care_task, update_care_task and create_calendar_event need the numeric id, and it must come from here, never from memory. The row with `is_you: true` is the authenticated vet. In a personal (solo) workspace the list comes back empty with a note: there is no team to assign to.

list_org_members

List the timeline of events (weights, prescriptions, exams, photos, vaccines, deaths, etc.) for one of the authenticated veterinarian's patients. Returns events newest-first, optionally filtered by type.

list_patient_events

List the authenticated veterinarian's patients. Supports an optional case-insensitive search across name, code, species, breed, microchip and guardian (responsável) name — multiple words narrow the match (e.g. 'amora maria' finds the patient Amora whose guardian is Maria) — plus pagination and sorting. Returns the paginated payload exactly as the app's API does, so result links/total can be used to fetch further pages.

list_patients

List prescriptions for the authenticated veterinarian across all patients. Status filter: 'pending' (AI suggestions awaiting approval), 'approved' (manually authored or already approved), or 'all' (default). Optional filters by patient, date range and free-text search.

list_prescriptions

List the vet's protocol templates (vacinação de filhote, pós-operatório, vermifugação...) with their steps. Use it BEFORE apply_protocol to find the correct protocol_template_id and confirm the steps with the vet. Step offsets are in days counted from the start date (offset_from 'start') or from the previous step ('previous_step').

list_protocol_templates

List the authenticated veterinarian's consultation sessions, newest first. Optional filters: patient_id (must belong to the user), date range (date_from / date_to), free-text search across transcription, summary, prontuário and linked patient/guardian fields. Each item includes the patient and guardian summaries plus counts for attachments, prescriptions and exams.

list_sessions

Mark a bill ("despesa", "conta a pagar") as paid: rent, a supplier, a commission bill. Requires the expense id from list_expenses plus its description for the safety check. A recurring bill gets its next occurrence created. Parked for the vet's explicit approval before executing, so never claim it was paid until the result confirms it. Refuses a bill that is already paid.

pay_expense

Register that a charge was paid (fully or partially). Requires the charge id from list_charges plus the payer name for the safety check, the amount in integer cents and the payment method kind. Parked for the vet's explicit approval before executing — never claim the payment was recorded until the result confirms it. Refuses drafts (confirm the charge first), quotes (accept them first), amounts above what is outstanding, and credit beyond the guardian's balance.

record_payment

Close one care task ("concluir lembrete") on the vet's AllEars.Vet agenda. The id and current title MUST come from a list_care_tasks/list_calendar result. Resolutions: 'completed' = done at this clinic (writes the clinical event; for vaccines pass applied_on/lot/manufacturer and next_due_on to auto-create the next dose reminder); 'completed_elsewhere' = guardian reports it was done elsewhere (requires reported_on; records an external event and the series continues); 'guardian_declined'; 'not_needed' (requires note); 'lost_to_follow_up'; 'superseded'. To just push the date, use snooze_care_task instead. The action is parked for the vet's explicit approval before executing — never claim the task is closed until the result confirms it.

resolve_care_task

Search the public AllEars.Vet veterinary reference hub: drug monographs by active ingredient (doses, contraindications, interactions), dog and cat breed profiles (including disease predispositions), vaccination protocols, and pet nutrition guides. Use this before answering any question about a drug dose, a vaccine schedule, a breed predisposition or a diet — it returns curated, cited data instead of recall. Follow up with show_reference_entry to read the full page.

search_reference

Build the WhatsApp collection message for a charge that ALREADY exists and is open ("manda a cobrança do Thor", "me dá o Pix da cobrança da Maria", "lembra a Maria que ela está devendo"). To bill something new ("cobra uma consulta da Maria"), create it first with create_charge. The message is: a friendly text with the outstanding amount and, when the practice has a Pix key, the Pix copia-e-cola code. Returns the text, a wa.me link that opens WhatsApp with it (to the guardian's phone when known) and the bare Pix code. It never sends anything: show the text and the link, and let the vet send it. Pass the charge id (from list_charges) or just the guardian_id: with one open charge it is used, with none or several the result says so. ALWAYS use this tool for a collection message and show its `text` exactly as returned: never write one yourself, because only this text carries the practice's real Pix code and whether a key is set.

show_collection_message

Fetch one clinic document (termo, atestado, declaração, laudo, autorização, …) belonging to the authenticated veterinarian: full body, title, kind, signature state (vet + responsável) and the linked patients/responsáveis. NOT for prescriptions — use show_prescription for receitas.

show_document

Fetch one guardian (responsável) belonging to the authenticated veterinarian, with the patients linked to them.

show_guardian

Fetch one of the authenticated veterinarian's patients with its guardians attached, plus a digest of its consultation history (recent_sessions: date, status and summary excerpt of the latest consultations, and sessions_count). Use list_sessions/show_session for full records. Returns 'not_found' if the patient id does not belong to the user.

show_patient

Fetch one prescription (a PatientEvent of type prescription) belonging to the authenticated veterinarian, with patient and consultation session attached.

show_prescription

Read a full page from the AllEars.Vet reference hub by section and slug (obtained from search_reference). Returns the structured data — dose table by species and route, vaccination schedule, breed predispositions, nutrient targets — plus the full text and the sources it cites. Always cite the returned url when you use this content.

show_reference_entry

Fetch one consultation session belonging to the authenticated veterinarian, including patient, guardians, attachments and the timeline of linked patient events (prescriptions, exams, weights, photos, etc.). Use this when the user asks about a specific consultation, asks for the prontuário, or asks 'what did I prescribe in session X'.

show_session

Snooze one care task ("adiar lembrete") on the vet's AllEars.Vet agenda until a future date. The id and current title MUST come from a list_care_tasks/list_calendar result. Snoozing is NOT completing — the task stays open and resurfaces on the new date; to close it use resolve_care_task. The action is parked for the vet's explicit approval before executing — never claim it moved until the result confirms it.

snooze_care_task

Update one event ("compromisso") on the vet's AllEars.Vet agenda. The id and current title MUST come from a list_calendar result. For a RECURRING event pass `scope`: 'this' edits only one occurrence, 'following' this and later ones (splits the series), 'series' everything (default) — 'this'/'following' also require the `occurrence_date` from the list_calendar row. Only send the fields being changed. The action is parked for the vet's explicit approval before executing — never claim it changed until the result confirms it.

update_calendar_event

Update one OPEN care task ("lembrete") on the vet's AllEars.Vet agenda: title, notes or due date. The id and current title MUST come from a list_care_tasks/list_calendar result. Moving a protocol step's date also shifts the steps chained after it. In a clinic it also reassigns the reminder (assigned_user_id + assigned_user_name from list_org_members), which moves its daily notification to that person. To close a task use resolve_care_task; to just push when it surfaces use snooze_care_task. The action is parked for the vet's explicit approval before executing — never claim it changed until the result confirms it.

update_care_task

Update fields on an existing guardian owned by the authenticated veterinarian. All fields are optional; pass only the ones you want to change. Pass 'patient_ids' to replace the linked patients. Pass 'append_notes' (not 'notes') to ADD to the existing observações without erasing them.

update_guardian

Update fields on an existing patient owned by the authenticated veterinarian. All fields are optional; pass only the ones you want to change. Pass 'guardian_ids' to replace the linked guardians. Pass 'append_notes' (not 'notes') to ADD to the existing observações without erasing them. Pass 'deceased_at' (ISO date) to register the patient's death; pair it with optional 'death_cause' and 'death_notes'. To clear a previously-recorded death, pass 'deceased_at' as null. To delete the patient, use the destructive 'delete_patient' tool instead. Returns 'not_found' if the patient is not owned by the user.

update_patient