Hypothesized structural use cases and technical implications

For instance internal corporate wiki. User should not be able to switch wiki or need to specify anything about the wiki to use. Perhaps the wiki is set via MCP config by the system admins, or perhaps they stuff the information into the LLM context in another way. Either way, set-wiki is not needed, and the optional arguments to change wiki should be ignored.

Supports multiple wikis. The wikis to use are not known in advance.

• No wiki argument or set-wiki call is needed. See "Why this works" example

Similar to last one.

• Slightly better served by having set-wiki, but unclear this justifies the added complexity. Also unclear how common and distinct of a use case this is. A chat about a single wiki might become a multi wiki chat later.

I use a single chat client and:

• I work with many wikis, but they are unrelated - likely no need to ever use multiple wikis in one session
• I need to interact with multiple wikis (very likely only 2) in the same session

In the first case the wiki context is set only once. In the second case the wiki context will likely be switched repeatedly.