Fact copy: MCP system knowledge for travel agencies

Factual summary

This knowledge page explains mcp system knowledge for travel agencies as an engineering and governance problem. It distinguishes protocol behaviour, travel-domain rules, system ownership and evidence required for production use.

Advisory workflow and responsibility

An agency assistant may retrieve customer context, compare offers, explain fare rules and prepare communication. Recommendation, reservation and binding booking remain distinct states so that a draft cannot become an external commitment accidentally.

Customer data should enter model context only for a defined purpose and case. The host filters capabilities by agency, role and booking record, while the server enforces the same object boundary independently.

Quality criteria

A useful system exposes sources and uncertainty, detects missing traveller data and escalates fare or visa questions it cannot establish reliably. Speed without traceability is not improved advisory quality.

Evaluation includes research time, system switches, correction rate, offer completeness, inappropriate data access and the number of cases that require safe human hand-off.