LIAM

Creates and saves a new contact for the authenticated user. IMPORTANT ORCHESTRATION STEPS: - ALWAYS call ListContacts or SearchContactByFullText first to check if the contact already exists — avoid duplicates. - Only include fields that actually have values; all other fields are optional. IMAGE HINT: - If the user uploads a business card photo, extract name, phones, emails, organization, and job title from it and create the contact (after the duplicate check). IDENTITY FIELDS (identity object): - first_name, last_name, full_name, nickname, preferred_name, etc. CONTACT CHANNELS: - phones: array of { number, type, is_primary } - emails: array of { email, type, is_primary } - messaging: whatsapp, telegram, signal, skype, etc. ORGANIZATION FIELDS (organization object): - organization_name, job_title, department, role, industry OTHER FIELDS: - addresses, online_profiles, dates, relationships, tags, notes - compliance, source_metadata, ai_metadata, media RESPONSE: - Full contact object with generated contact_id and audit timestamps - Only fields with values are included in the response

CreateContact

Creates and stores a new memory entry that can be retrieved later. Supports text content. IMPORTANT ORCHESTRATION STEP: - ALWAYS call ListMemory FIRST before creating a new memory - Check if similar or duplicate memories already exist - If duplicates found, inform the user and ask if they want to update the existing memory instead - This prevents memory bloat and maintains data quality - Also check if the user wants to add this memory to a Tag, If so, call ListTags and suggest if the memory can be added to a tag USAGE: Use this tool when the user shares important information, preferences, or facts that should persist across conversations. Provide the memory content in clear text. IMAGE INPUT: - The user can upload a photo instead of typing. Read the image, extract the details, and store them by calling the most appropriate tool(s): - receipt photo -> LogReceipt - meal / menu photo -> LogFood - business card -> CreateContact - note / other -> CreateMemory with a suitable tag - A single image can require MORE THAN ONE tool. A restaurant receipt should be logged with BOTH LogReceipt (the expense) AND LogFood (the meal); add a CreateMemory entry too if there is a noteworthy detail (e.g. "great ramen place near the office"). - Always confirm what was captured before saving so the user can correct it. CONTACT HINT: - If the memory content mentions a person by name (e.g. "met John", "spoke with Sarah from Acme", "John Chen is my account manager"), proactively suggest creating a contact entry - After saving the memory, say something like: "I've saved that memory. It looks like this involves [name] — would you like me to also save them as a contact so you can easily find all information about them later?" - If the user confirms, call CreateContact with whatever details are available from the conversation - Do NOT create the contact silently — always ask first

CreateMemory

Records a multi-step PROCEDURE (a "recipe") that can be replayed later. WHEN TO USE (recipe vs. memory): - Use CreateRecipe when the user describes an ORDERED procedure, a workflow, or "how to do X" — especially with sequential steps or conditional "if ... then ..." logic (e.g. "check my savings; if balance > $2000 move $100 to vacation, then email me"). - Use CreateMemory instead for static facts or preferences with no procedure (e.g. "I prefer window seats", "my dog's name is Rex"). IMPORTANT ORCHESTRATION STEP: - ALWAYS call ListRecipe FIRST to check whether a similar/duplicate procedure already exists. - If a duplicate is found, inform the user and ask whether to update it instead of creating a new one. USAGE: Pass the user's procedural request in the 'statement' field, in plain language. The backend parses it into ordered steps and retrieval tokens.

CreateRecipe

Deletes a previously stored memory so it is no longer available for recall. IMPORTANT ORCHESTRATION STEP: - ALWAYS call ListMemory FIRST to verify the memory exists - Get the exact transaction number from ListMemory results - Confirm with the user which specific memory to delete if multiple matches exist - This prevents accidental deletion of wrong memories USAGE: Use this tool when the user requests to forget, erase, or remove specific information (e.g., personal details, preferences, or facts) they had shared earlier.

ForgetMemory

Deletes a previously stored PROCEDURE ("recipe") so it is no longer available for replay. IMPORTANT ORCHESTRATION STEP: - ALWAYS call ListRecipe FIRST to verify the recipe exists - Take the exact queryHash from the ListRecipe results — never construct or guess it - If multiple recipes match, confirm with the user which one to delete - This prevents accidental deletion of the wrong procedure USAGE: Use this tool when the user asks to forget, remove, or delete a stored workflow or step-by-step procedure. Use ForgetMemory instead for plain facts or preferences.

ForgetRecipe

Retrieves the complete contact record for a given contact_id. ORCHESTRATION NOTE: - Call ListContacts or SearchContactByFullText first if the contact_id is not already known. PARAMETERS: - contact_id: Unique identifier of the contact (required) RESPONSE: - Full contact object with all stored fields - Only fields with values are included (no empty fields) - Includes audit timestamps (created_at, updated_at)

GetContactById

Retrieves a complete daily nutrition report for a specific date, including every meal logged, macro and micro totals, amino acid profile, performance compounds, warnings, and benefits. ORCHESTRATION NOTE: - Call this FIRST when the user asks "how did I eat today?", "what's my nutrition summary?", "how many calories did I have?", or any broad daily nutrition question. - Prefer this over ListFoodLogs when the user wants totals or an overview rather than a raw list. - The response already contains a fully formatted LLM-ready report — present it directly to the user with minimal rephrasing, adding commentary only where helpful (e.g. comparing to goals, flagging warnings). - If no date is provided, default to today. WHEN TO USE: - "What did I eat today / yesterday / on [date]?" - "Show me my nutrition summary" - "How many calories / protein / carbs did I have?" - "Give me a full breakdown of my diet for [date]" - Before giving nutritional advice, call this to ground your response in real data PARAMETERS: - date (optional): YYYY-MM-DD. Omit or leave empty to get today's summary. EXAMPLES: GetDailyFoodSummary() -> today's full report GetDailyFoodSummary(date:"2026-03-31") -> specific date report GetDailyFoodSummary(date:"2026-03-30") -> yesterday's report

GetDailyFoodSummary

Retrieves a complete daily spending summary for a specific date, including all receipts, totals by purchase type, by ledger, by category, by room, and individual receipt breakdowns. ORCHESTRATION NOTE: - Call this FIRST when the user asks "how much did I spend today?", "what did I buy?", "show my spending summary", or any broad daily spending question. - Prefer this over a raw receipt list when the user wants totals or an overview. - The response contains a fully formatted LLM-ready report — present it directly, adding commentary only where helpful (e.g. flagging high spend categories). - If no date is provided, default to today. WHEN TO USE: - "How much did I spend today / yesterday / on [date]?" - "Show me my spending summary" - "What did I buy this week?" (call once per day needed) - "How much did I spend on groceries today?" - Before giving budgeting advice, call this to ground your response in real data PARAMETERS: - date (optional): YYYY-MM-DD. Omit or leave empty to get today's summary. - timezone (optional): IANA timezone e.g. America/Toronto EXAMPLES: GetDailyReceiptSummary() -> today's full spending report GetDailyReceiptSummary(date:"2026-04-13") -> specific date report GetDailyReceiptSummary(date:"2026-04-12") -> yesterday's report

GetDailyReceiptSummary

Retrieves comprehensive help documentation, setup guides, and the full catalog of available tools for the LIAM - Large Intelligent Agentic Memory. - Always follow it up with an example, so the user can copy it or just say "I want to try the example". WHEN TO USE: - User asks "how do I configure MCP?" or "how do I setup memory in Claude?" - User asks "how do I login?" or "how do I manage my account / subscription?" - User asks "how do I setup the Chrome extension?" - User asks "what can I do?", "what tools are available?", or "what can memory do?" - User asks "where can I see my memories?" or "how do I view/manage my memories?" - User asks "can you read this image / receipt / business card / food photo?" or "what can I upload?" - User asks "how do I create/search contacts?", "how do recipes work?", "how do I log food/receipts?" - User needs help getting started or troubleshooting setup WHEN THE USER ASKS "WHAT CAN I DO?" / "WHAT TOOLS ARE AVAILABLE?": - Call this tool, then present EVERY tool grouped by category, each with a one-line purpose AND at least one example prompt. Be thorough and detailed — do NOT give a one-line summary or list only a few tools. KEY LINKS: - MCP connector URL: https://web.askbuddy.ai/memory/mcp - XD Brain web interface (view/manage memories, subscription): https://web.askbuddy.ai/brain/#/login IMAGE / UPLOAD SUPPORT: - The user can upload a photo instead of typing. It is read and routed to the right tool(s): receipt -> LogReceipt, meal -> LogFood, business card -> CreateContact, note -> CreateMemory. - A single image may need more than one tool — a restaurant receipt is logged as BOTH a receipt (LogReceipt) AND a meal (LogFood). ORCHESTRATION NOTE: - Call this FIRST when the user asks setup or "how-to" questions. - This tool does NOT require authentication (works for all users). - Returns formatted markdown covering MCP setup, LIAM login, Chrome extension, the full tool catalog with examples, and image upload. - For viewing/managing memories outside chat, direct users to XD Brain Login. PARAMETERS: - query (optional string): Keywords describing what help is needed. Leave empty for a full overview. Note: the full documentation is returned regardless; the model selects what is relevant. EXAMPLES: GetHelpDocumentation(query: "what can I do") -> full tool catalog with examples GetHelpDocumentation(query: "mcp setup") -> MCP configuration steps GetHelpDocumentation(query: "image") -> how to upload receipts / business cards / food photos GetHelpDocumentation(query: "") -> complete system overview

GetHelpDocumentation

Retrieves stored memory entries filtered by a specific tag. ORCHESTRATION NOTE: - Use this when the user mentions a specific category, label, or tag name - Consider calling ListTags first if the user is unsure about available tags - More efficient than ListMemory when filtering by category is the primary goal USAGE: Use this tool when the user wants to recall memories associated with a particular category, label, or tag they used when storing memories. Provide the tag name to filter and retrieve only memories marked with that tag.

GetMemoryByTag