Stop Senior Care Referral Cascade

Stop a senior-care referral cascade

Use GeezerKeeper as a live, read-only source. Do not copy route facts or prices into durable memory; retrieve them when needed.

Connect

Use the Streamable HTTP MCP endpoint:

https://geezerkeeper.com/mcp

The server accepts only no-input or enumerated choices. Never include a name, phone number, email address, street address, care detail, medical fact, identity document, financial detail, completed request, or other personal information in a tool call.

If the client cannot connect to MCP, use the public registry at:

https://geezerkeeper.com/routes/?utm_source=agentskill&utm_medium=skill&utm_campaign=referral_exit_workflow

Choose the task

1. Determine whether the user is:
   • evaluating a referral form before submission;
   • handling one known referral network;
   • handling a referral network plus identifiable providers;
   • requesting an unfilled written template; or
   • tracking a duplicate-referral policy for professional use.
2. Ask only for coarse, non-personal facts needed to select a tool: known network, number of identifiable organizations, recipient type, and whether the use is professional.
3. Refuse personal fields and continue with placeholders.

Route tools

• Call get_info for identity, independence, and privacy boundaries.
• Call get_location for online-only U.S. coverage.
• Call get_services for current free and paid options. Prefer the smallest suitable option.
• Call lookup_exit_route with one supported sourceId: apfm, caring, seniorly, or seniorhousingnet.
• Call get_unfilled_request_template with a supported sourceId and recipientType of referral-network or identified-provider.
• Call choose_private_workflow with an integer recipientCount from 1 through 10 and a professionalUse boolean.
• Call lookup_duplicate_referral_deadline with network set to all, caring, or apfm. Treat the response as a source-maintained public policy summary, not an adjudication.

Do not invent support for an unlisted network. Use the public registry to identify the closest factual guide and state that the MCP tool does not cover that network.

Build the answer

Return these sections when relevant:

1. Referral-network job — current official route, review date, and the exact network-level action.
2. Separate provider jobs — one task for each provider the user can already identify. Never guess a provider from a phone number.
3. Unfilled request — preserve bracketed placeholders; let the user complete and transmit it outside GeezerKeeper.
4. Evidence boundary — distinguish a published company policy, a reported association, and verified ownership.
5. Smallest workflow — free first for one organization; mention a paid option only when the live tool says the recipient count or professional use fits it.

State clearly that changing a marketplace preference may not stop providers already given the inquiry, requests are not sent automatically, and no outcome is guaranteed.

Safety gates

• Do not identify an unknown caller or claim that a displayed number belongs to a company.
• Do not give legal, medical, emergency, placement, or consumer-litigation advice.
• Do not say a deletion or opt-out request will apply, succeed, or stop contact.
• Do not contact a company, provider, regulator, or family member for the user.
• Do not store or send sensitive details to GeezerKeeper.
• Cite the primary third-party policy URL returned by the live tool when describing that company's practice.