hys_activity_logs_list
ChatGPTUse this when an authenticated HYS admin needs permitted activity history and full activity metadata from their organization or HYS workspace. In admin-facing text, call the scope their organization or HYS workspace. Use workspace-wide activity only when the admin explicitly asks for organization/workspace activity, a timeframe, or a specific activity type. If the admin only asks to check activity or show recent activity without a donor, recipient, record, timeframe, organization/workspace scope, or activity type, answer directly with one short follow-up question before calling this tool, such as "Which donor, recipient, or timeframe should I use?" Do not create a plan or call this tool first. If the admin uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor, recipient, record, or timeframe, answer directly with one short follow-up question before calling this tool, such as "Which donor or recipient should I look up?" Do not create a plan or call this tool first.
hys_activity_logs_list
ChatGPTUse this when an authenticated HYS admin needs permitted activity history and full activity metadata from their organization or HYS workspace. In admin-facing text, call the scope their organization or HYS workspace. Use workspace-wide activity only when the admin explicitly asks for organization/workspace activity, a timeframe, or a specific activity type. If the admin only asks to check activity or show recent activity without a donor, recipient, record, timeframe, organization/workspace scope, or activity type, answer directly with one short follow-up question before calling this tool, such as "Which donor, recipient, or timeframe should I use?" Do not create a plan or call this tool first. If the admin uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor, recipient, record, or timeframe, answer directly with one short follow-up question before calling this tool, such as "Which donor or recipient should I look up?" Do not create a plan or call this tool first.
hys_activity_logs_list
ChatGPTUse this when an authenticated HYS admin needs permitted activity history and full activity metadata from their organization or HYS workspace. In admin-facing text, call the scope their organization or HYS workspace. Use workspace-wide activity only when the admin explicitly asks for organization/workspace activity, a timeframe, or a specific activity type. If the admin only asks to check activity or show recent activity without a donor, recipient, record, timeframe, organization/workspace scope, or activity type, answer directly with one short follow-up question before calling this tool, such as "Which donor, recipient, or timeframe should I use?" Do not create a plan or call this tool first. If the admin uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor, recipient, record, or timeframe, answer directly with one short follow-up question before calling this tool, such as "Which donor or recipient should I look up?" Do not create a plan or call this tool first.
hys_aggregate_query
ChatGPTUse this when an authenticated HYS admin asks for exact fundraising totals, counts, rankings, or grouped donation analytics, such as top donors, giving by payment method, gifts by program, donors by state, monthly revenue, or designation totals. Use this instead of listing donation pages for analytic or leaderboard questions. For simple "how much by payment method" or "giving by payment method" prompts, request metrics ["total_amount","donation_count"], sort by total_amount desc, use a modest limit such as 20, and include labels. Only request average_amount or largest_gift when the admin asks for averages, largest gifts, or deeper gift-size analysis.
hys_aggregate_query
ChatGPTUse this when an authenticated HYS admin asks for exact fundraising totals, counts, rankings, or grouped donation analytics, such as top donors, giving by payment method, gifts by program, donors by state, monthly revenue, or designation totals. Use this instead of listing donation pages for analytic or leaderboard questions. For simple "how much by payment method" or "giving by payment method" prompts, request metrics ["total_amount","donation_count"], sort by total_amount desc, use a modest limit such as 20, and include labels. Only request average_amount or largest_gift when the admin asks for averages, largest gifts, or deeper gift-size analysis.
hys_aggregate_query
ChatGPTUse this when an authenticated HYS admin asks for exact fundraising totals, counts, rankings, or grouped donation analytics, such as top donors, giving by payment method, gifts by program, donors by state, monthly revenue, or designation totals. Use this instead of listing donation pages for analytic or leaderboard questions. For simple "how much by payment method" or "giving by payment method" prompts, request metrics ["total_amount","donation_count"], sort by total_amount desc, use a modest limit such as 20, and include labels. Only request average_amount or largest_gift when the admin asks for averages, largest gifts, or deeper gift-size analysis.
hys_capabilities
ChatGPTUse this first when an authenticated HYS admin asks what fundraising analysis HYS can do, what questions are possible, what metrics, reports, donor segments, data-quality checks, codebook labels, saved filters, saved reports, groupings, or limitations are supported, or what to analyze next. This capability-discovery tool returns supported analysis surfaces and the correct next tools; it does not return live dashboard totals. Do not call dashboard, report, saved-filter, form, program, donor-list, or donation-summary tools before this for capability-discovery prompts.
hys_capabilities
ChatGPTUse this first when an authenticated HYS admin asks what fundraising analysis HYS can do, what questions are possible, what metrics, reports, donor segments, data-quality checks, codebook labels, saved filters, saved reports, groupings, or limitations are supported, or what to analyze next. This capability-discovery tool returns supported analysis surfaces and the correct next tools; it does not return live dashboard totals. Do not call dashboard, report, saved-filter, form, program, donor-list, or donation-summary tools before this for capability-discovery prompts.
hys_capabilities
ChatGPTUse this first when an authenticated HYS admin asks what fundraising analysis HYS can do, what questions are possible, what metrics, reports, donor segments, data-quality checks, codebook labels, saved filters, saved reports, groupings, or limitations are supported, or what to analyze next. This capability-discovery tool returns supported analysis surfaces and the correct next tools; it does not return live dashboard totals. Do not call dashboard, report, saved-filter, form, program, donor-list, or donation-summary tools before this for capability-discovery prompts.
hys_codebook
ChatGPTUse this when an authenticated HYS admin needs human-readable labels for donation methods, donation types, transaction statuses, designations, programs, or forms so answers do not expose raw codes or unlabeled internal IDs. When another HYS tool returns program, form, or designation IDs, pass those exact IDs in ids so labels are complete even in large HYS workspaces.
hys_codebook
ChatGPTUse this when an authenticated HYS admin needs human-readable labels for donation methods, donation types, transaction statuses, designations, programs, or forms so answers do not expose raw codes or unlabeled internal IDs. When another HYS tool returns program, form, or designation IDs, pass those exact IDs in ids so labels are complete even in large HYS workspaces.
hys_codebook
ChatGPTUse this when an authenticated HYS admin needs human-readable labels for donation methods, donation types, transaction statuses, designations, programs, or forms so answers do not expose raw codes or unlabeled internal IDs. When another HYS tool returns program, form, or designation IDs, pass those exact IDs in ids so labels are complete even in large HYS workspaces.
hys_commitments_get
ChatGPTUse this when an authenticated HYS admin needs to get a single sponsorship or commitment record by ID.
hys_commitments_get
ChatGPTUse this when an authenticated HYS admin needs to get a single sponsorship or commitment record by ID.
hys_commitments_get
ChatGPTUse this when an authenticated HYS admin needs to get a single sponsorship or commitment record by ID.
hys_commitments_list
ChatGPTUse this when an authenticated HYS admin needs to list sponsorship or commitment records with simple workspace-safe filters suitable for automation workflows.
hys_commitments_list
ChatGPTUse this when an authenticated HYS admin needs to list sponsorship or commitment records with simple workspace-safe filters suitable for automation workflows.
hys_commitments_list
ChatGPTUse this when an authenticated HYS admin needs to list sponsorship or commitment records with simple workspace-safe filters suitable for automation workflows.
hys_dashboard_brief
ChatGPTUse this when an authenticated HYS admin asks for a concise daily admin brief, board-prep summary, or quick health check across their organization or HYS workspace. Returns aggregate donor, recipient, sponsorship, donation, and watch-item signals without individual donor, gift, note, activity, or sponsorship rows. For precise current dashboard totals, date-bounded counts, or unusual live-count checks, use hys_dashboard_snapshot instead. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, reports, or next analyses HYS can do; use hys_capabilities first. Use detail tools only after the admin asks who, which record, notes, or recent activity.
hys_dashboard_brief
ChatGPTUse this when an authenticated HYS admin asks for a concise daily admin brief, board-prep summary, or quick health check across their organization or HYS workspace. Returns aggregate donor, recipient, sponsorship, donation, and watch-item signals without individual donor, gift, note, activity, or sponsorship rows. For precise current dashboard totals, date-bounded counts, or unusual live-count checks, use hys_dashboard_snapshot instead. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, reports, or next analyses HYS can do; use hys_capabilities first. Use detail tools only after the admin asks who, which record, notes, or recent activity.
hys_dashboard_brief
ChatGPTUse this when an authenticated HYS admin asks for a concise daily admin brief, board-prep summary, or quick health check across their organization or HYS workspace. Returns aggregate donor, recipient, sponsorship, donation, and watch-item signals without individual donor, gift, note, activity, or sponsorship rows. For precise current dashboard totals, date-bounded counts, or unusual live-count checks, use hys_dashboard_snapshot instead. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, reports, or next analyses HYS can do; use hys_capabilities first. Use detail tools only after the admin asks who, which record, notes, or recent activity.
hys_dashboard_snapshot
ChatGPTUse this when an authenticated HYS admin asks for actual current dashboard totals, a high-level snapshot, quick overview, or unusual live-count check across their HYS workspace: donors, recipients, sponsorships, and donations. Do not use this for capability-discovery questions such as what fundraising analysis HYS can do, what questions are possible, what metrics, donor segments, reports, labels, or groupings are supported, or what to analyze next; use hys_capabilities first for those. In admin-facing text, call this their organization or HYS workspace and avoid internal architecture labels. Avoid listing individual donor, gift, or sponsorship rows unless the admin explicitly asks who or which records.
hys_dashboard_snapshot
ChatGPTUse this when an authenticated HYS admin asks for actual current dashboard totals, a high-level snapshot, quick overview, or unusual live-count check across their HYS workspace: donors, recipients, sponsorships, and donations. Do not use this for capability-discovery questions such as what fundraising analysis HYS can do, what questions are possible, what metrics, donor segments, reports, labels, or groupings are supported, or what to analyze next; use hys_capabilities first for those. In admin-facing text, call this their organization or HYS workspace and avoid internal architecture labels. Avoid listing individual donor, gift, or sponsorship rows unless the admin explicitly asks who or which records.
hys_dashboard_snapshot
ChatGPTUse this when an authenticated HYS admin asks for actual current dashboard totals, a high-level snapshot, quick overview, or unusual live-count check across their HYS workspace: donors, recipients, sponsorships, and donations. Do not use this for capability-discovery questions such as what fundraising analysis HYS can do, what questions are possible, what metrics, donor segments, reports, labels, or groupings are supported, or what to analyze next; use hys_capabilities first for those. In admin-facing text, call this their organization or HYS workspace and avoid internal architecture labels. Avoid listing individual donor, gift, or sponsorship rows unless the admin explicitly asks who or which records.
hys_donations_get
ChatGPTUse this when an authenticated HYS admin needs details for one donation by ID from their HYS workspace. Include donor details only when the admin's HYS permission set covers that donor profile.
hys_donations_get
ChatGPTUse this when an authenticated HYS admin needs details for one donation by ID from their HYS workspace. Include donor details only when the admin's HYS permission set covers that donor profile.
hys_donations_get
ChatGPTUse this when an authenticated HYS admin needs details for one donation by ID from their HYS workspace. Include donor details only when the admin's HYS permission set covers that donor profile.
hys_donations_list
ChatGPTUse this when an authenticated HYS admin explicitly asks for individual donation records, who gave recently, donor names, donor emails, or a recent gift list from their HYS workspace. For high-level snapshots, board prep, or "anything unusual" prompts, use hys_dashboard_snapshot and hys_donations_summary with recent_limit 0 instead. Include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donations_list
ChatGPTUse this when an authenticated HYS admin explicitly asks for individual donation records, who gave recently, donor names, donor emails, or a recent gift list from their HYS workspace. For high-level snapshots, board prep, or "anything unusual" prompts, use hys_dashboard_snapshot and hys_donations_summary with recent_limit 0 instead. Include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donations_list
ChatGPTUse this when an authenticated HYS admin explicitly asks for individual donation records, who gave recently, donor names, donor emails, or a recent gift list from their HYS workspace. For high-level snapshots, board prep, or "anything unusual" prompts, use hys_dashboard_snapshot and hys_donations_summary with recent_limit 0 instead. Include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donations_summary
ChatGPTUse this when an authenticated HYS admin asks for donation totals, counts, averages, recent donation patterns, stewardship signals, or board/admin brief metrics for their HYS workspace. For high-level briefs, board prep, snapshot, or "anything unusual" prompts, use aggregate summary fields and keep recent_limit at 0. Do not request recent rows for broad snapshots. For grouped fundraising analytics such as giving by payment method, top donors, monthly revenue, or designation totals, prefer hys_aggregate_query. Payment-method summary rows include method_label; present that label first and do not ask the admin to confirm HYS method codes; use hys_codebook when a complete donation-method label glossary is needed. Only set recent_limit above 0 when the admin explicitly asks who gave, which individual gifts, donor names, donor emails, or a recent gift list. When recent rows are requested, include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donations_summary
ChatGPTUse this when an authenticated HYS admin asks for donation totals, counts, averages, recent donation patterns, stewardship signals, or board/admin brief metrics for their HYS workspace. For high-level briefs, board prep, snapshot, or "anything unusual" prompts, use aggregate summary fields and keep recent_limit at 0. Do not request recent rows for broad snapshots. For grouped fundraising analytics such as giving by payment method, top donors, monthly revenue, or designation totals, prefer hys_aggregate_query. Payment-method summary rows include method_label; present that label first and do not ask the admin to confirm HYS method codes; use hys_codebook when a complete donation-method label glossary is needed. Only set recent_limit above 0 when the admin explicitly asks who gave, which individual gifts, donor names, donor emails, or a recent gift list. When recent rows are requested, include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donations_summary
ChatGPTUse this when an authenticated HYS admin asks for donation totals, counts, averages, recent donation patterns, stewardship signals, or board/admin brief metrics for their HYS workspace. For high-level briefs, board prep, snapshot, or "anything unusual" prompts, use aggregate summary fields and keep recent_limit at 0. Do not request recent rows for broad snapshots. For grouped fundraising analytics such as giving by payment method, top donors, monthly revenue, or designation totals, prefer hys_aggregate_query. Payment-method summary rows include method_label; present that label first and do not ask the admin to confirm HYS method codes; use hys_codebook when a complete donation-method label glossary is needed. Only set recent_limit above 0 when the admin explicitly asks who gave, which individual gifts, donor names, donor emails, or a recent gift list. When recent rows are requested, include donor contact fields only for donor profiles covered by the admin's HYS permission set.
hys_donor_data_quality_summary
ChatGPTUse this first, and usually only, when an authenticated HYS admin asks for exact donor contactability or data-cleanup counts, such as how many donors do not have usable mailing addresses, partial addresses, emails, phones, or email-suppressed records. It already counts normalized fields and mapped custom address/contact fields, so do not inspect forms or page through donor records first. For "do not have usable mailing addresses", request missing_address and partial_address, then sum those counts in the answer.
hys_donor_data_quality_summary
ChatGPTUse this first, and usually only, when an authenticated HYS admin asks for exact donor contactability or data-cleanup counts, such as how many donors do not have usable mailing addresses, partial addresses, emails, phones, or email-suppressed records. It already counts normalized fields and mapped custom address/contact fields, so do not inspect forms or page through donor records first. For "do not have usable mailing addresses", request missing_address and partial_address, then sum those counts in the answer.
hys_donor_data_quality_summary
ChatGPTUse this first, and usually only, when an authenticated HYS admin asks for exact donor contactability or data-cleanup counts, such as how many donors do not have usable mailing addresses, partial addresses, emails, phones, or email-suppressed records. It already counts normalized fields and mapped custom address/contact fields, so do not inspect forms or page through donor records first. For "do not have usable mailing addresses", request missing_address and partial_address, then sum those counts in the answer.
hys_donors_get
ChatGPTUse this when an authenticated HYS admin needs to get a donor core profile by ID. Include related sponsorships, donations, household, or commitments only when explicitly needed; set related_limit when a bounded collection response is required. For MCP tool calls, collection relation includes default to 10 rows unless related_limit is provided.
hys_donors_get
ChatGPTUse this when an authenticated HYS admin needs to get a donor core profile by ID. Include related sponsorships, donations, household, or commitments only when explicitly needed; set related_limit when a bounded collection response is required. For MCP tool calls, collection relation includes default to 10 rows unless related_limit is provided.
hys_donors_get
ChatGPTUse this when an authenticated HYS admin needs to get a donor core profile by ID. Include related sponsorships, donations, household, or commitments only when explicitly needed; set related_limit when a bounded collection response is required. For MCP tool calls, collection relation includes default to 10 rows unless related_limit is provided.
hys_donors_list
ChatGPTUse this when an authenticated HYS admin explicitly asks to list individual donor records or browse donor profiles. Do not use this to compute exact donor data-quality counts by paging donor records. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For exact high-level counts or organization overviews, use hys_dashboard_snapshot; for concise daily briefs, board prep, or quick health checks, use hys_dashboard_brief instead of listing donor records.
hys_donors_list
ChatGPTUse this when an authenticated HYS admin explicitly asks to list individual donor records or browse donor profiles. Do not use this to compute exact donor data-quality counts by paging donor records. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For exact high-level counts or organization overviews, use hys_dashboard_snapshot; for concise daily briefs, board prep, or quick health checks, use hys_dashboard_brief instead of listing donor records.
hys_donors_list
ChatGPTUse this when an authenticated HYS admin explicitly asks to list individual donor records or browse donor profiles. Do not use this to compute exact donor data-quality counts by paging donor records. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For exact high-level counts or organization overviews, use hys_dashboard_snapshot; for concise daily briefs, board prep, or quick health checks, use hys_dashboard_brief instead of listing donor records.
hys_donors_lookup
ChatGPTUse this when an authenticated HYS admin wants to find a donor by name, email, phone, or searchable donor text and return a bounded donor snapshot in one read-only call. Use hys_donors_search for result lists and hys_donors_get when the donor id is already known. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries; ask which donor when the reference is ambiguous.
hys_donors_lookup
ChatGPTUse this when an authenticated HYS admin wants to find a donor by name, email, phone, or searchable donor text and return a bounded donor snapshot in one read-only call. Use hys_donors_search for result lists and hys_donors_get when the donor id is already known. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries; ask which donor when the reference is ambiguous.
hys_donors_lookup
ChatGPTUse this when an authenticated HYS admin wants to find a donor by name, email, phone, or searchable donor text and return a bounded donor snapshot in one read-only call. Use hys_donors_search for result lists and hys_donors_get when the donor id is already known. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries; ask which donor when the reference is ambiguous.
hys_donors_search
ChatGPTUse this when an authenticated HYS admin needs to find donors by name, email, phone, username, organization name, or custom donor fields within their permitted donor forms. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries. Do not use donor search to compute exact donor data-quality counts. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For broad segment, count, or ranking questions, use hys_segment_query or hys_aggregate_query instead.
hys_donors_search
ChatGPTUse this when an authenticated HYS admin needs to find donors by name, email, phone, username, organization name, or custom donor fields within their permitted donor forms. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries. Do not use donor search to compute exact donor data-quality counts. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For broad segment, count, or ranking questions, use hys_segment_query or hys_aggregate_query instead.
hys_donors_search
ChatGPTUse this when an authenticated HYS admin needs to find donors by name, email, phone, username, organization name, or custom donor fields within their permitted donor forms. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor queries. Do not use donor search to compute exact donor data-quality counts. For questions such as how many donors lack usable mailing addresses, email, or phone, use hys_donor_data_quality_summary instead. For broad segment, count, or ranking questions, use hys_segment_query or hys_aggregate_query instead.
hys_entities_get
ChatGPTUse this when an authenticated HYS admin needs to get a single entity (recipient) by ID with optional related data (program, sponsors).
hys_entities_get
ChatGPTUse this when an authenticated HYS admin needs to get a single entity (recipient) by ID with optional related data (program, sponsors).
hys_entities_get
ChatGPTUse this when an authenticated HYS admin needs to get a single entity (recipient) by ID with optional related data (program, sponsors).
hys_entities_list
ChatGPTUse this when an authenticated HYS admin needs to list entities (recipients/beneficiaries) with optional filtering by program_id, sponsorship status, and recipient search text. If the user gives a program name, first use hys_programs_list to resolve the allowed program id, then call this tool with program_id and sponsorship_status/status. Do not put a program name in search; search is for recipient fields such as name, email, sponsorship number, tags, and profile fields.
hys_entities_list
ChatGPTUse this when an authenticated HYS admin needs to list entities (recipients/beneficiaries) with optional filtering by program_id, sponsorship status, and recipient search text. If the user gives a program name, first use hys_programs_list to resolve the allowed program id, then call this tool with program_id and sponsorship_status/status. Do not put a program name in search; search is for recipient fields such as name, email, sponsorship number, tags, and profile fields.
hys_entities_list
ChatGPTUse this when an authenticated HYS admin needs to list entities (recipients/beneficiaries) with optional filtering by program_id, sponsorship status, and recipient search text. If the user gives a program name, first use hys_programs_list to resolve the allowed program id, then call this tool with program_id and sponsorship_status/status. Do not put a program name in search; search is for recipient fields such as name, email, sponsorship number, tags, and profile fields.
hys_filters_list
ChatGPTUse this when an authenticated HYS admin needs to review saved views or saved report filters available to their permission set. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_filters_list
ChatGPTUse this when an authenticated HYS admin needs to review saved views or saved report filters available to their permission set. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_filters_list
ChatGPTUse this when an authenticated HYS admin needs to review saved views or saved report filters available to their permission set. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_forms_list
ChatGPTUse this when an authenticated HYS admin needs donor or recipient profile form definitions they can access, usually before field-specific donor or recipient filtering. Do not use this for exact donor data-quality count questions about usable mailing addresses, email, phone, or cleanup totals; use hys_donor_data_quality_summary first because it already counts normalized and mapped custom fields. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first.
hys_forms_list
ChatGPTUse this when an authenticated HYS admin needs donor or recipient profile form definitions they can access, usually before field-specific donor or recipient filtering. Do not use this for exact donor data-quality count questions about usable mailing addresses, email, phone, or cleanup totals; use hys_donor_data_quality_summary first because it already counts normalized and mapped custom fields. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first.
hys_forms_list
ChatGPTUse this when an authenticated HYS admin needs donor or recipient profile form definitions they can access, usually before field-specific donor or recipient filtering. Do not use this for exact donor data-quality count questions about usable mailing addresses, email, phone, or cleanup totals; use hys_donor_data_quality_summary first because it already counts normalized and mapped custom fields. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first.
hys_notes_list
ChatGPTUse this when an authenticated HYS admin needs recent stewardship notes for one donor or recipient they are allowed to view in their organization or HYS workspace. If the admin only asks to check notes, or uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor or recipient, answer directly with one short follow-up question such as "Which donor or recipient should I look up?" instead of guessing, searching for the app/workspace name, creating a plan, or calling this tool.
hys_notes_list
ChatGPTUse this when an authenticated HYS admin needs recent stewardship notes for one donor or recipient they are allowed to view in their organization or HYS workspace. If the admin only asks to check notes, or uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor or recipient, answer directly with one short follow-up question such as "Which donor or recipient should I look up?" instead of guessing, searching for the app/workspace name, creating a plan, or calling this tool.
hys_notes_list
ChatGPTUse this when an authenticated HYS admin needs recent stewardship notes for one donor or recipient they are allowed to view in their organization or HYS workspace. If the admin only asks to check notes, or uses an ambiguous pronoun such as their, that donor, or that recipient without a resolved donor or recipient, answer directly with one short follow-up question such as "Which donor or recipient should I look up?" instead of guessing, searching for the app/workspace name, creating a plan, or calling this tool.
hys_programs_list
ChatGPTUse this when an authenticated HYS admin needs to list the programs and campaigns they are allowed to see, or when a user gives a program/campaign name before asking for recipients, sponsorships, notes, activity, or reports. Resolve the program id here first, then pass that id to recipient/entity tools such as hys_entities_list. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_programs_list
ChatGPTUse this when an authenticated HYS admin needs to list the programs and campaigns they are allowed to see, or when a user gives a program/campaign name before asking for recipients, sponsorships, notes, activity, or reports. Resolve the program id here first, then pass that id to recipient/entity tools such as hys_entities_list. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_programs_list
ChatGPTUse this when an authenticated HYS admin needs to list the programs and campaigns they are allowed to see, or when a user gives a program/campaign name before asking for recipients, sponsorships, notes, activity, or reports. Resolve the program id here first, then pass that id to recipient/entity tools such as hys_entities_list. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, or reports HYS can do; use hys_capabilities first.
hys_records_get
ChatGPTUse this to fetch the HYS donor, recipient, or donation record identified by a search result id such as donor:123, entity:456, or donation:789. Results are limited to the authenticated admin's HYS workspace and permission set.
hys_records_get
ChatGPTUse this to fetch the HYS donor, recipient, or donation record identified by a search result id such as donor:123, entity:456, or donation:789. Results are limited to the authenticated admin's HYS workspace and permission set.
hys_records_get
ChatGPTUse this to fetch the HYS donor, recipient, or donation record identified by a search result id such as donor:123, entity:456, or donation:789. Results are limited to the authenticated admin's HYS workspace and permission set.
hys_reports_list
ChatGPTUse this when an authenticated HYS admin needs saved report definitions and schedule metadata they are permitted to view.
hys_reports_list
ChatGPTUse this when an authenticated HYS admin needs saved report definitions and schedule metadata they are permitted to view.
hys_reports_list
ChatGPTUse this when an authenticated HYS admin needs saved report definitions and schedule metadata they are permitted to view.
hys_segment_query
ChatGPTUse this when an authenticated HYS admin asks who belongs in a donor segment, such as lapsed donors, addressable donors, donors in a state, donors over a giving threshold, monthly-giving prospects, or donors who gave in one period but not another. This performs server-side filtering and returns names, contactability, giving metrics, lifecycle flags, and next-action hints without paging through raw donor records.
hys_segment_query
ChatGPTUse this when an authenticated HYS admin asks who belongs in a donor segment, such as lapsed donors, addressable donors, donors in a state, donors over a giving threshold, monthly-giving prospects, or donors who gave in one period but not another. This performs server-side filtering and returns names, contactability, giving metrics, lifecycle flags, and next-action hints without paging through raw donor records.
hys_segment_query
ChatGPTUse this when an authenticated HYS admin asks who belongs in a donor segment, such as lapsed donors, addressable donors, donors in a state, donors over a giving threshold, monthly-giving prospects, or donors who gave in one period but not another. This performs server-side filtering and returns names, contactability, giving metrics, lifecycle flags, and next-action hints without paging through raw donor records.
hys_snapshot_widget_render
ChatGPTUse this only after a real read-only HYS data tool has already returned structuredContent that should be shown as a compact visual snapshot in a compatible app UI. First call the needed read-only HYS tool, then pass that tool's structuredContent directly as this tool's arguments. Do not invent or reuse unstated data for this tool. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first. This presentation-only tool does not fetch records or bypass the admin's HYS permission set.
hys_snapshot_widget_render
ChatGPTUse this only after a real read-only HYS data tool has already returned structuredContent that should be shown as a compact visual snapshot in a compatible app UI. First call the needed read-only HYS tool, then pass that tool's structuredContent directly as this tool's arguments. Do not invent or reuse unstated data for this tool. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first. This presentation-only tool does not fetch records or bypass the admin's HYS permission set.
hys_snapshot_widget_render
ChatGPTUse this only after a real read-only HYS data tool has already returned structuredContent that should be shown as a compact visual snapshot in a compatible app UI. First call the needed read-only HYS tool, then pass that tool's structuredContent directly as this tool's arguments. Do not invent or reuse unstated data for this tool. Do not use this for broad capability-discovery questions about what fundraising analysis, metrics, segments, labels, groupings, or reports HYS can do; use hys_capabilities first. This presentation-only tool does not fetch records or bypass the admin's HYS permission set.
hys_system_context
ChatGPTUse this when an authenticated HYS admin needs to confirm their connected HYS workspace, current user, granted scopes, and enabled read surfaces. If the admin asks what fundraising analysis HYS can do, what questions are possible, or what metrics, segments, reports, or groupings are supported, use hys_capabilities next before dashboard, program, form, or saved-filter tools. In admin-facing text, use only organization, HYS workspace, or our data for the data boundary; avoid internal architecture labels.
hys_system_context
ChatGPTUse this when an authenticated HYS admin needs to confirm their connected HYS workspace, current user, granted scopes, and enabled read surfaces. If the admin asks what fundraising analysis HYS can do, what questions are possible, or what metrics, segments, reports, or groupings are supported, use hys_capabilities next before dashboard, program, form, or saved-filter tools. In admin-facing text, use only organization, HYS workspace, or our data for the data boundary; avoid internal architecture labels.
hys_system_context
ChatGPTUse this when an authenticated HYS admin needs to confirm their connected HYS workspace, current user, granted scopes, and enabled read surfaces. If the admin asks what fundraising analysis HYS can do, what questions are possible, or what metrics, segments, reports, or groupings are supported, use hys_capabilities next before dashboard, program, form, or saved-filter tools. In admin-facing text, use only organization, HYS workspace, or our data for the data boundary; avoid internal architecture labels.
search
ChatGPTUse this when an authenticated HYS admin wants to find donors or recipients by name, email, or other searchable text. Use hys_records_get with a returned result id to inspect a full record. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor or recipient queries; ask which donor or recipient when the record reference is ambiguous.
search
ChatGPTUse this when an authenticated HYS admin wants to find donors or recipients by name, email, or other searchable text. Use hys_records_get with a returned result id to inspect a full record. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor or recipient queries; ask which donor or recipient when the record reference is ambiguous.
search
ChatGPTUse this when an authenticated HYS admin wants to find donors or recipients by name, email, or other searchable text. Use hys_records_get with a returned result id to inspect a full record. Do not treat app, connector, environment, or workspace labels such as HYS or HelpYouSponsor as donor or recipient queries; ask which donor or recipient when the record reference is ambiguous.
