Goodword

Get a composed briefing for a window: meetings, reminders due, and top recommendations. Each recommendation has `warmthDecayFlag`, true only for a warm contact whose last recorded activity was more than 60 days ago: say Goodword has no recorded contact with them in the last two months, not that the user hasn't been in touch or that the relationship is fading. It is false when warmth is below the warm threshold, when there is no recorded activity at all, or when Goodword could not check, so do not read false as recent contact. `today` and `week` look ahead from now; `yesterday` looks back over the previous day. If a section failed to load, its name appears in `degradedSections` -- treat that section as unknown/failed, not as confirmed empty. When you tell the user about these people, talk in plain words, not field names: "not a direct contact; reachable through Priya", or "may be reachable through Priya" when the link is unconfirmed, not "bridge" or "extended network". Never say the user knows someone they do not know directly. Say what Goodword observed, such as when you last met or how often you talk, not how close they are, unless the user said so. Call someone "not a direct contact" only when they are not one, and never tell the user they do not know someone: Goodword cannot tell. Do not label direct contacts. Never put a warmth value or other score to the user, and never rank or compare people by how close they are or how well the user knows them: when asked, give what was observed for each and let the user judge. A missing record is not a fact about the user's life: say "the last recorded contact was in March", not "you haven't been in touch" or "you last spoke in March"; treat a person with no details as unknown, not ruled out; and never say "only" or "no one else" about people you have not looked at. What the user tells you in the conversation is newer than the record. Warmth has no history, so never claim a relationship is warming up or cooling off. Before you reply, do the read-only lookups the user's request calls for instead of offering them: read the user's history with a connector before recommending them, and search the user's contacts for someone who fits a need the record mentions. When the user asks how to reach someone, wants to reconnect or asks what you suggest about reaching or writing to someone, offer to draft the message (to the connector, for someone who is not a direct contact), and do not call draft_outreach; only when the user explicitly asks for a note or message ("draft a note to Jonah", "I want to send Dana a note"), read the relationship with get_relationship_context first, then call draft_outreach for a direct contact rather than offering to, and use its draft rather than writing the message yourself, without making it longer; never call it for someone who is not a direct contact (`isExtendedNetwork: true`): say they are not a direct contact and offer to draft a note to the connector instead. A draft says only what the record or the user supports: state a recorded moment as what happened, never invent the user's feelings, memories, plans or contact that neither the record nor the user shows, and never imply such contact or feeling with words like "again", "still" or "since then" ("Thanks for the slides", not "Thanks again for the slides"); if you remove such a sentence, add no placeholder (a stored draft may be sent unfilled): tell the user in one short line which sentence you removed. Describe what you found, not how the tools work, then end with the user's one next step.

get_briefing

Get members of a specific group. Use get_groups first to find the group ID. Returns a JSON array of member profiles with name, position, company, and contact details — or a short plain-language message if the group is still being built or has no members yet. Page through large groups by raising skip.

get_group_members

Get your Goodword groups with member counts. Groups organize your contacts into meaningful lists. Returns group ID, name, type, description, and member count.

get_groups

Get introductions you've created or received. Filter by status to see pending, accepted, or declined intros.

get_intros

Explain the user's Goodword network using bounded, privacy-safe insights. Omit contactId for network-wide composition and activity aggregates such as warm ties, dormant relationships, bridge worlds, hubs, communities, and recurring topics. Pass a contact ID from search_contacts to learn whether that person is a direct contact or extended-network person, how the user is connected, and the available relationship, activity, community, warm-path, bridge, and recent-change evidence. Responses use explicit status and reason fields: null data with unsupported means the feature is disabled, unavailable means no fresh aggregate exists, and not_found means the profile is not visible. An available connection path with an empty connectedThrough list means the lookup succeeded but found no named path; null means unavailable or not applicable.

get_network_insights

Get AI-ranked contact recommendations — people Goodword thinks you should reconnect with or nurture. Each recommendation includes the person's name, reason for recommendation, goal label, and contact details. Returns a count of recommended people and a flat list of them. Optionally filter to a specific goal.

get_recommendations

Get your reminders (20 by default, up to 100 with take, most overdue first). Returns each reminder's text, due date, priority tier, completion status, and linked contact, plus pagination (total, hasMore, nextSkip) so you can tell when more exist than are shown and fetch the next page with skip set to nextSkip.

get_reminders

List, add, update, or complete the user's networking goals; call add when the user states a goal, call list first to get a goal's ID before update or complete, and call complete once a goal has been achieved or is no longer relevant.

manage_goals

Remove a contact from an existing group. Use get_groups to find the group ID and get_group_members to confirm the profile ID before removing them.

remove_group_member

Search across the user's Goodword contacts and notes. Returns matching results with an id usable with fetch, a display title, and a deep link.

search

Search your Goodword network by name, company, or freetext query. Results contain two different kinds of people. Direct contacts are people in the user's network. Extended-network people (isExtendedNetwork: true) are people the user does NOT know directly but can likely reach through a champion in their network. For extended-network results: bridges lists the champions who connect the user to this person (each with id, name, and confirmed, true when the link is corroborated; a bridge id is a contact ID usable with get_contact_profile to look up that champion), extendedConfirmed is true when at least one bridge is confirmed, and sources names the platforms the relationship was observed on (linkedin, x, instagram). When presenting an extended-network person, always distinguish them from direct contacts and say who they are reachable through. get_contact_profile works for both kinds; extended-network people return public info only. Use this to find contacts before using other tools that require a contact ID.

search_contacts

Create a reminder, optionally about a contact. Supports one-time and recurring reminders. Invoke proactively when the user commits to a future action ("I should follow up with her next month", "remind me to check in after the launch") or when a conversation ends with an open loop that has a natural date.

set_reminder

Replace the relationship story for a contact: how the user met them and their shared history. Invoke proactively when the user explains how they know someone. This overwrites the whole existing story and cannot be undone: first read the current howWeMet with get_relationship_context (include: ["profile"], no purpose), merge the new detail into it, and confirm the merged text with the user before calling. Use search_contacts first to find the contact ID.

update_connection_context