Orendro

Use this when creating or updating one profile goal.

goal_upsert

Use this first when the user asks about goals, goal setup, or how to set goals.

goals_list

Use this when the user wants to view the interactive Orendro groceries card. This single tool fetches authenticated data and renders the card. The optional range changes only the authenticated dashboard projection.

groceries_card_get

Use this when listing grocery items approaching expiry.

grocery_inventory_expiring

Use this when listing current grocery inventory and quantities.

grocery_inventory_list

Use this when you have a confirmation token and need to remove a grocery item.

grocery_inventory_remove_confirm

Use this when removing a grocery item and a confirmation token is required.

grocery_inventory_remove_prepare

Use this when adding or updating a grocery item. Name and quantity are required; infer category and unit when recognizable, default acquired_at to today when useful, and avoid blank expires_at values. If the user does not specify an expiry date, use online lookup when available for the item or packaging; otherwise best-guess a conservative shelf-life from the item/category/acquired_at and log that estimate. Omit expires_at only when the item is too unclear to estimate.

grocery_inventory_upsert

Use this for profile-wide setup status only, not for goal discovery or goal recommendations. For goal questions, use goals_list first.

health_profile_summary_get

Use this when you have a confirmation token and should execute a bulk workout/cardio history deletion.

history_delete_confirm

Use this when the user asks to delete multiple workout/cardio history entries, including deleting all workout and cardio history.

history_delete_prepare

Use this when listing instruction/configuration documents available to the app.

instructions_list_docs

Use this when reading one instruction document by relative path.

instructions_read_doc

Use this when retrieving notes for an exact date.

memory_notes_get_by_date

Use this when listing the newest memory notes.

memory_notes_list_recent

Use this when full-text searching notes and memory chunks.

memory_notes_search

Use this when calculating total alcohol intake for a date range.

nutrition_alcohol_get_total

Use this when the user wants to view the interactive Orendro nutrition card. This single tool fetches authenticated data and renders the card. The optional range changes only the authenticated dashboard projection.

nutrition_card_get

Use this when logging a food or drink entry for the user. Only item_name is required by schema, but agents should strongly prefer submitting a complete best-effort nutrition estimate whenever the item and serving are recognizable. If the user did not provide nutrition details, estimate meal_type, quantity, calories, protein_g, carbs_g, fat_g, and alcohol_ml when applicable using common nutrition knowledge, known restaurant/packaged-food data, prior user logs, or a reasonable serving-size assumption. Do not ask follow-up questions merely because calories or macros were omitted. Omit calorie or macro fields only when the item or serving is too ambiguous to produce a useful estimate. When values are estimated, say so in notes and include brief uncertainty or provenance. This guidance should encourage complete logs but must not make macros required or block logging.

nutrition_log_create

Use this to correct an existing nutrition log entry in place. Prefer this over delete-and-recreate when the user corrects an item, serving, calories, macros, sodium, alcohol, meal type, or notes. Supply only fields that should change.

nutrition_log_update

Use this when you have a confirmation token and should delete nutrition log entries.

nutrition_logs_delete_confirm

Use this when deleting nutrition log entries and a confirmation token is required.

nutrition_logs_delete_prepare

Use this when you need all food/alcohol entries for a specific date.

nutrition_logs_get_day

Use this when summarizing food logs and macros over a date range.

nutrition_logs_get_range_summary

Call this when onboarding_status says setup is incomplete. Ask the returned question naturally and wait for the answer. onboarding_update will return the following question, so do not call this again after every saved answer.

onboarding_next

Use this when checking Orendro setup progress or deciding whether to continue guided onboarding. This is never a prerequisite for normal Orendro reads or writes, which must remain available during incomplete setup.

onboarding_status

Save the user's answer to onboarding_next with this tool. It can also skip a step, request target estimates, or accept reviewed estimates. After it succeeds, ask the next question returned in this tool result immediately; do not stop after merely confirming what was saved.

onboarding_update

Use this when reading the authenticated user's profile basics.

profile_get

Use this when updating profile basics: display name, timezone, birthday, height, sex, or activity factor.

profile_update

Use this for a focused, bounded lookup of structured records by domain, date, tags, or keyword. Results contain stable record identifiers and curated user-facing fields; choose one domain instead of all when the request is domain-specific.

records_query

Render the Orendro summary card. You must call daily_summary_get first, then pass its structured result unchanged as the summary argument. This tool validates presentation data and does not fetch or modify Orendro records.

render_daily_summary_card

Use this when the user wants to view the interactive Orendro time card. This single tool fetches authenticated data and renders the card. The optional range changes only the authenticated dashboard projection.

time_card_get

Use this when listing the authenticated user's active time categories.

time_category_list

Use this when creating or updating a time category for the authenticated user.

time_category_upsert

Use this when listing time entries across a date range or by category/project/search.

time_entries_list

Use this when you have a confirmation token and should delete time entries.

time_entry_delete_confirm

Use this when deleting one or more time entries and a confirmation token is required.

time_entry_delete_prepare

Use this when the user wants to abandon the current active time timer.

time_entry_discard

Use this when the user says finished, done, or stopped and you should close the active timer entry. If entry_id is not provided, finish the current active entry.

time_entry_finish

Use this when logging time for completed work, chores, personal tasks, learning, or other manual time entries. Infer category and title when obvious, do not ask follow-up questions when the title, category, or duration can be reasonably inferred, and put uncertainty in notes instead. When the user clearly gives a duration, log it immediately; when started_at and ended_at are both present, duration_minutes may be derived from them. If the user is still doing the task and wants an active timer, use time_entry_start instead, even when the start time needs to be backdated.

time_entry_log