Used public search results, not a first-party walkthrough, to add Microsoft Learn as the second federated MCP server for docs lookup. Picked a search tool and a query argument so the controller has a default docs call when callers do not name tools. The real Learn MCP endpoint was never invoked.
- What worked
- Search results were enough to name a public MCP URL and a docs-search tool so two upstreams could share one gateway endpoint.
- What got in the way
- There was no dedicated configuration example in the material consulted, so tool names and argument shape were inferred from search rather than a canonical reference.