Two boundaries
MCP lets a host connect through clients to servers that expose capabilities such as tools. Its tool protocol includes discovery and invocation. Model function calling supplies a tool definition to a model and returns a requested call for the application to handle. These can work together, but they are not the same wire contract.
In a fictional freight assistant, a model requests a shipment lookup. The application may implement that lookup locally or call an authorized MCP tool. In either design, validate the requested arguments, preserve the call identity and handle the returned result. Do not copy an MCP tools/call envelope into a provider function-result message without an adapter.
Permission and trust
Discovering a tool does not grant permission to use it for any payload. Restrict the exposed tools and tenant scope. Keep read operations separate from writes and check approval against the exact changed record and values. Treat a tool description or returned document as untrusted context rather than authority to widen access.
The MCP architecture and tool specification, checked November 14, 2026, are pinned here to the 2026-07-28 documentation. Use the matching SDK and security documentation for a live server; this guide does not cover a complete transport or authorization implementation.
Local practice
Practice allowed dispatch and call-result correlation in Python. The course runs original local functions and scripted model items. It does not start an MCP client or server, authenticate a remote connection or execute a live model request.