Update to IMO Health MCP Server

{
  "description": "Set up the IMO Health plugin after installation, guide account connection through the host OAuth flow, and verify access with a read-only terminology lookup.",
  "included_files": [],
  "name": "imo-setup",
  "skill_md_contents": "---\r\nname: imo-setup\r\ndescription: Set up the IMO Health plugin after installation, guide account connection through the host OAuth flow, and verify access with a read-only terminology lookup.\r\n---\r\n\r\n# Set up IMO Health\r\n\r\nUse this skill when the user runs plugin setup or asks to connect their IMO account.\r\n\r\n1. Explain that the plugin connects to the existing IMO Health service and requires an account with the relevant API permissions. Never ask for passwords, client secrets, access tokens, or refresh tokens in chat or files.\r\n2. Inspect tools exposed by the installed plugin. If the connection is missing, guide the user to the plugin's account/connection settings and the host's Connect or Sign in action. Use the supported host connection flow if available; let the user complete IMO sign-in, MFA, and consent on the provider page. Do not construct an OAuth authorization URL yourself or implement a token exchange in chat.\r\n3. A publisher configuring the provided OAuth client must enter its client secret only into the host's secure connection setup and register the exact redirect URI shown there with IMO. A regular installing user should only sign in and consent. If setup lacks a supported secure secret-entry flow, explain that publisher connection setup is still required. Do not switch to unauthenticated access or change the client method.\r\n4. After linking, verify with one read-only call: normalize the synthetic term `hypertension` in the Problem domain using the exposed normalization tool's actual input schema. A read-only test is part of this setup workflow. Do not perform additional enrichment, refinement, NLP, or relationship queries.\r\n5. Report the actual returned title and lexical_code. Report setup as verified only when an authenticated call succeeds. Tool visibility alone is insufficient. A no-match response can establish service access, but report the lookup as no match. If there is an authentication error, guide reconnection. A permission error needs the corresponding IMO scope or entitlement. A redirect mismatch needs the publisher to register the host's exact callback URI. Never fabricate a successful connection.\r\n6. If tools appear only in new conversations, explain that limitation and ask the user to start a new chat with this plugin selected. Do not create a chat unless requested.\r\n\r\nThe host controls when OAuth appears. Setup runs after installation when the user chooses setup; declaring onboarding does not force consent to complete inside the installation dialog.\r\n"
}