Add a database login for ToolUniverse

Most ToolUniverse tools need no login. A few databases require the user's own free or licensed account. The person you are helping is usually a scientist, not a programmer: explain in plain words, one step at a time.

Never ask the user to paste a key, token or password into the chat, and never put one in a file, command or message yourself. Keys are typed only into the ToolUniverse website (hosted use) or the user's own local settings (local use).

1. Find out which login is needed

• If a tool failed, its error names the missing or rejected setting (for example OMIM_API_KEY). Use that exact name.
• If the user asks in general, ask what they want to do, and suggest only the logins that unlock it. Do not push them to collect every key.

Common ones:

The full list, with steps for each, is on https://connect.aiscientist.tools/credentials (search box). Before the user signs up for anything paid, metered, or requiring a license or an institutional claim, say so and let them decide.

2. Get the key (the user does this)

Give the link and the two or three clicks needed, from the table or the credentials page. Suggest the least access the site offers (read-only). If the key arrives by email, the user opens it themselves.

3. Save it where ToolUniverse can use it

Hosted ToolUniverse (the usual case: the assistant is connected to connect.aiscientist.tools):

1. Open https://connect.aiscientist.tools/credentials.
2. Find the database (search by name), paste the key into its box, click Save key.

It is stored encrypted and used only when a tool that needs it runs for this user. You never see it.

Local ToolUniverse (ToolUniverse runs on this computer, for example uvx tooluniverse or a Python install): the setting is an environment variable with the exact name, for example OMIM_API_KEY. Tell the user to add it to their own shell profile or the .env file their setup uses, in their editor; do not write the value yourself. Restart the assistant afterwards.

4. Check it works

Run the tool that needed it again with a small, public example (for OMIM, a well-known gene such as BRCA1). Then tell the user plainly which of these happened:

• It works: done.
• Still "missing": the key was saved under a different name, or the page was not saved. Check the exact name.
• "Rejected" or "unauthorized": the database did not accept the key (typo, not activated yet, or the account lacks API access). For OMIM and UMLS, approval can take days.
• A different error: the database may be down or rate-limiting. Try later; it is not the login.

Never show a tool output that contains the key. If one does, tell the user to replace the key on the provider's site and save the new one.