Named tools and JSON schemas make intent and input boundaries explicit.
How it works
A three-stage, human-confirmed process
- Chat-guided cloud organization: A persistent assistant helps collect the information. The browser masks direct identifiers before guided cloud chat or note organization, and gpt-oss:120b-cloud creates a structured draft through the localhost Ollama proxy.
- Human confirmation: The patient or caregiver corrects and confirms every item. Unconfirmed data cannot enter matching or WebMCP.
- Regional search: A visible bilingual query bridge sends exact curated cancer terms to TFDA in Traditional Chinese and ClinicalTrials.gov in English. Search then follows Taiwan, Asia, and worldwide, with registry sources, update dates, unknown criteria and next questions.
Why WebMCP matters
The website defines safe tools instead of making an agent guess the interface.
TrialBridge TW exposes structured, browser-discoverable capabilities for method explanation, public registry search, pending-requirement review, confirmed-result explanation, an unsent outreach draft, and a source-traceable care-team discussion brief. Public tools are always available. Confirmed-context tools appear only after confirmation and visible WebMCP permission.
The available tools change with the confirmed profile, pending questions, results, and permission state.
Raw notes are unavailable; no tool can enroll, submit, send, schedule, or change treatment.
A clinical-trial registry describes a research plan, not proof of benefit. Final eligibility must be determined by the study team.