Update to Cerca.me

{
  "description": "Use Cerca when the user wants to recall, save, rate, annotate or remove places, plan travel from their own place history and friends' picks, compare places with someone, or import places and shared Google Maps lists.",
  "included_files": [
    {
      "relative_path": "references/tools.md",
      "size_in_bytes": 2396
    }
  ],
  "name": "places-and-trip-planning",
  "skill_md_contents": "---\nname: places-and-trip-planning\ndescription: Use Cerca when the user wants to recall, save, rate, annotate or remove places, plan travel from their own place history and friends' picks, compare places with someone, or import places and shared Google Maps lists.\n---\n\n# Use Cerca as the user's place memory\n\nUse the connected Cerca MCP server and its actual tool schemas. Sign in through\nthe host's OAuth connection flow if access is needed; keep credentials out of\nmessages and files. See [tool guide](references/tools.md) for supported inputs.\n\n## Plan a trip or decide where to go\n\n1. Call `get_travel_context` first with the destination and, when known, its\n   center latitude and longitude. Clarify ambiguous destinations.\n2. Put the user's `want_to_go` places first. Treat `loved` as the strongest\n   personal signal; use `get_taste_profile` for broader preferences.\n3. Exclude `avoid` places from recommendations. Keep friends' recommendations\n   attributed to the named people returned. Credit `cerca_picks` and\n   `cerca_rating` to Cerca separately.\n4. When a person is named, use `compare_with_friend`; `list_friends` can resolve\n   a name to a username. Ask when a match needs confirmation. Do not reveal\n   private want-to-go notes belonging to anyone else.\n5. Ground names, statuses, notes, links and place facts in returned data.\n   Explain gaps and pagination. Never invent hours, availability or bookings.\n\n`search_places` searches Cerca's catalogue. It does not search Google or the\nweb. The assistant can use other available search tools for new discoveries\nand then, when requested, save them to Cerca. Do not misattribute those\ndiscoveries to a Cerca search result.\n\n## Record places\n\n- Use `save_place` for somewhere the user wants to try and `rate_place` for\n  somewhere they visited. Valid ratings are `loved`, `liked`, `meh`, `disliked`.\n- Prefer an exact `place_ref` returned by Cerca. Otherwise supply a Google\n  Maps place URL or name plus location. If `needs_confirmation` is returned,\n  ask the user to choose a candidate; retry with that candidate's real ref.\n- Want-to-go notes are private. Rating notes are public on the user's profile.\n  Explain that visibility and ask before publishing personal information.\n- Saving with a nonblank note can replace an existing private note.\n  `update_note` replaces the current note; an empty string clears it.\n- Rating a saved place removes its want-to-go save, including its private note.\n  Explain this consequence when moving an existing save to a rating. Obtain\n  confirmation for replacements or deletion when the user's request has not\n  already authorized that exact change.\n- Confirm with the user before `remove_place`. It removes their save or rating\n  and associated note. It does not delete the shared place or anyone else's data.\n- Inspect mutation results before claiming success. A tool may return an error,\n  `already_saved`, `already_rated`, `needs_confirmation`, or another outcome.\n\n## Import places\n\nUse `import_places` for 1–25 items with per-item status and place identity.\nInspect every result; ask about unresolved candidates and explain skipped or\nfailed items. Batch ratings have the same visibility and replacement effects.\n\nUse `import_google_maps_list` only for a shared list URL supplied by the user.\nIt starts a background import. Report that it started, then use\n`get_import_status` with the returned import ID; do not claim completion until\nthe returned status says so. Imports are limited to three per user per day.\nCerca cannot read all private Google lists or continuously synchronize them.\n\n## Respect access and service limits\n\nA read-only connection cannot mutate places. Explain how to reconnect with\nwrite access through the host. Do not work around OAuth scopes or profile\nprivacy. Reauthentication, exhausted lookup budgets and provider errors must\nbe reported accurately. Prefer catalogue results and returned refs to avoid\nunnecessary external lookups; never retry repeatedly to bypass quotas.\n\nCerca cannot reserve tables, book accommodation, buy tickets, charge a card,\nor manage another user's account. Explain those limits without invoking\nunrelated tools or claiming unsupported actions succeeded.\n"
}