"LIFX" matching MCP tools:

• get_peopleA

  Dayze — Life ContextB

  List the authenticated user's CRM people. Each person includes avatar_url, photo_count, and has_photos; use get_person_photos(person_id) for the full gallery. Notes omitted by default (has_notes flag); pass include_notes=true for progressive fetch (credential/secret spans are redacted server-side). Supports limit (default 100, max 500) and offset; returns total and truncated. Requires OAuth or a supported scoped credential. ($0.10; API key required)

  ConnectorNo auth

• get_person_neighborhoodA

  Dayze — Life ContextB

  Subgraph around one user-owned person_id — profile (avatar_url, photo_count, has_photos) plus declared connections. Use get_person_photos for the full gallery. Notes omitted unless include_notes=true (redacted). Requires OAuth or a supported scoped credential. ($0.15; API key required)

  ConnectorNo auth

• search_modelsA

  EOSL.ai — Hardware End-of-Life DatabaseA

  Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Read-only. Returns up to 10 families with status, EOSL window, and page URL. Use this for discovery when you have a name; for an exact part number use lookup_part, and use get_family with a returned slug for the full record.

  ConnectorNo auth

• list_vendorsA

  EOSL.ai — Hardware End-of-Life DatabaseA

  List all vendors tracked by EOSL.ai with family counts and vendor page URLs. Read-only, no parameters. Use this first to check whether a vendor is covered at all; for specific models use search_models, for a part number use lookup_part.

  ConnectorNo auth

• reset_trackerA

  Dayze — Life ContextB

  MUTATES a sobriety/streak tracker for the authenticated user (sets current value to 0 and restarts the clock). Prefer tracker_id from get_trackers, or tracker_title fuzzy match. Optional reset_at (ISO) and note. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• read_gmail_attachmentA

  Dayze — Life ContextB

  Download one Gmail attachment by message_id + attachment_id (from read_gmail_message.attachments). Returns utf-8 text for text/csv/vcf/vcard; binary types return filename/mime/size + a note (no base64 dump). Optional account. Read-only. Share tokens cannot call. ($0.10; API key required)

  ConnectorNo auth

• set_primary_person_nameA

  Dayze — Life ContextB

  Rename a CRM contact’s canonical name and refresh slug. By default preserves the old name as a former_name alias. Prefer this over create+merge for spelling fixes. Dayze is the context layer — bounded mutation only. ($0.10; API key required)

  ConnectorNo auth

• get_city_summaryA

  cityparity — Cost-of-Living & Quality-of-Life ComparisonA

  Concise profile of one city: currency, tax shape (bracket count + top rate + payroll/national insurance), headline costs (rent / groceries / transit / childcare), safety-net values (parental leave, vacation, universal healthcare), and data freshness. Lighter than compare_cities; use when the user is asking about one place rather than a comparison. On parental leave, quote safety_net.parental_leave_summary rather than building your own sentence: some countries (Ireland, Australia, the UK, Czechia, part of Sweden) pay a flat weekly cash sum instead of a share of salary, so parental_leave_paid_pct is 0 or partial for them and stating it alone would wrongly call their leave unpaid. safety_net.avg_commute_minutes is a ONE-WAY commute, a single leg rather than a daily round trip: report it as "about N minutes each way", and double it yourself if the user asked what they spend commuting per day. It is door to door, averaged over every commuter regardless of mode, for the metro area, and excludes people who work from home. Read-only, no side effects; returns a text summary plus structured JSON.

  ConnectorNo auth

• search_gmailA

  Dayze — Life ContextB

  Search one of the authenticated user's connected Gmail inboxes (read-only). Reuses Integrations hub Gmail (service_connections provider=gmail). Optional account/email selects a mailbox when multiple are connected — call list_gmail_accounts first. Prefer Gmail operators: from:, subject:, is:unread, newer_than:7d, has:attachment. Returns id, subject, from, date, snippet only (no body). Follow up with read_gmail_message. Cannot send, archive, or delete. Never invent email contents. If Gmail is not connected, connect at /integrations. Requires API key or OAuth with scope context. Share tokens cannot call this tool. ($0.10; API key required)

  ConnectorNo auth

• log_favorite_songA

  Dayze — Life ContextB

  MUTATES the authenticated user favorite tracks list at /music. Use when they favorite or save a song — do not store this as a chat memory or in music_preferences. Example: “Henry Mancini - Piano And Strings (1995 Remastered)” → log_favorite_song({ track: "Henry Mancini - Piano And Strings (1995 Remastered)" }) or title + artist. Optional year_note, source_url. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• resolve_personA

  Dayze — Life ContextB

  Resolve a nickname or surface name to a CRM person via person_aliases → exact name → slug → unique substring. Returns avatar_url, photo_count, has_photos, and photos[{url,is_primary}] preview; use get_person_photos for full gallery. Notes omitted unless include_notes=true (redacted). Prefer this before money or relationship tools when the agent only has a nickname. ($0.05; API key required)

  ConnectorNo auth

• get_memoriesA

  Dayze — Life ContextB

  Authenticated user memories from Dayze Agent. Pass query for semantic/keyword retrieval. Prefer search for event-first trip and calendar titles. Requires OAuth or a supported scoped credential. ($0.10; API key required)

  ConnectorNo auth

• searchA

  Dayze — Life ContextB

  Search the authenticated user life graph. Deterministic routing first: food + relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Requires OAuth or a supported scoped credential. ($0.15; API key required)

  ConnectorNo auth

• compare_citiesA

  cityparity — Cost-of-Living & Quality-of-Life ComparisonA

  Compare two cities for one household: take-home pay, full cost breakdown, the equivalent target salary needed to match source net cash, non-cash lifestyle deltas (vacation, parental leave, healthcare), and a 0-100 quality score on five weighted dimensions. Use this for a head-to-head between two named cities; for a single city call get_city_summary, and to rank many cities call rank_cities. Read-only, no side effects; returns a text summary plus structured JSON. RSU income is NOT a parameter; RSU is treated as source-only because grants typically do not follow you across employers.

  ConnectorNo auth

• get_methodologyA

  life. scored.A

  Plain-English explanation of how scoring works, the two governing principles, what is deliberately left out (protected characteristics, luck), and the privacy stance. Use to answer "how does this work / is this fair" questions.

  ConnectorNo auth

• lookup_partA

  EOSL.ai — Hardware End-of-Life DatabaseA

  Look up one hardware part number or model name in the EOSL.ai database (read-only, no auth; for many parts use bulk_check). Returns support status, End-of-Sale and End-of-Service-Life dates, support runway score, and the primary vendor bulletin URL backing the dates. Matching is exact, then punctuation-insensitive, then Fortinet short-SKU aliases (FG-60E -> FortiGate-60E); a model/family name (e.g. "7010TX-48") that matches no SKU returns the family-level record, flagged matchedVia:family-name. Anything else returns found:false rather than a guessed date.

  ConnectorNo auth

• bulk_checkA

  EOSL.ai — Hardware End-of-Life DatabaseA

  Check up to 200 part numbers in one call (read-only, no auth; for a single part use lookup_part). Returns a per-part row (status, EOSL date, source URL, page URL) plus summary counts: past, endingSoon, supported, active, notFound. Never partial and never destructive: unknown or malformed entries do not fail the call, each simply returns found:false in its row.

  ConnectorNo auth

• update_personA

  Dayze — Life ContextB

  MUTATES the authenticated user CRM. Patch one existing person they own (person_id UUID required). Optional fields: name (renames + refreshes slug), is_favorite, tier (vip|normal|low), relationship, notes (replaces stored notes — read first if you need to append), birthday (YYYY|YYYY-MM|YYYY-MM-DD|MM-DD|--MM-DD or null to clear; MM-DD stores month_day precision). Rejects unknown fields. Does not create or delete people. Rebuilds life_state so the next get_context_pack inner_circle is fresh. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• log_foodA

  Dayze — Life ContextB

  MUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. Example: “I had Mee Pok for late lunch with my parents” → log_food({ what: "Mee Pok", kind: "meal", meal_period: "late lunch", with: ["my parents"] }). Optional: place/merchant, amount, consumed_at (ISO). Resolves with/Mum/Dad via person aliases; unknown names do not fail the food write. Tags companions on the mirrored event. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• log_eventA

  Dayze — Life ContextB

  MUTATES the authenticated user calendar. Use for non-food days — funeral, cremation, appointment, dinner, anything that is not a food log. Do not store this as a chat memory. Example (funeral tonight): log_event({ title: "Funeral service — Mr Goh Choo Taw", date: "2026-08-29", time: "8pm", location: "Multi Purpose Hall, Blk 661 Jurong West St 64", category: "funeral" }). Example (Sunday cremation): log_event({ title: "Cremation — Mr Goh Choo Taw", date: "2026-08-30", location: "Mandai Crematorium", category: "funeral" }). Required: title + event_date (YYYY-MM-DD, YYYY-MM, or YYYY; alias date). Soft dates expand to first-of-period and set metadata.date_precision (day|month|year|approx). Optional: event_time (8pm or 20:00; alias time), end_date, end_time, location / city+country, description, category, external_url, visibility (private|friends|public), image_url, timezone, date_precision, share_with (Dayze handles e.g. ["boof"]), people / with / person_ids, idempotency_key (recommended; retries reuse the first write). For trips/residences prefer log_travel({ city, country, start_date, kind }). Unknown people names do not fail the write. Public events return share_url (/e/{id}) for Explore + social. Inserts public.events, optional event_people / shared_events, then rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• delete_eventA

  Dayze — Life ContextB

  MUTATES by removing one existing calendar event the authenticated user owns. Required: event_id (UUID). Unknown or other-user event_id returns an error. event_people tags cascade; linked entity_assets are archived. When the event mirrors a Food Diary row (external_source user_food_log), the food row is deleted too. For food-diary meals, prefer delete_food. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  Connector

  Destructive

  No auth