Somehow make UniProt info more "Claude accessible"

[Tom Goddard]

I just tried to prod Claude into selecting the S4 voltage sensor helix of pdb 9my3. It tried valiantly but repeatedly only came up with a typical range for these potassium channels of 220-245. Opening the uniprot annotations in ChimeraX shows under Features / Transmembrane regions S4 is 217-232. Claude kept begging me to look at the uniprot page or ChimeraX uniprot features and tell it the answer, but I refused. I'm trying to think of how Claude can extract this info from ChimeraX commands. It opened the uniprot annotations but the command return value didn't have the details. Maybe for use with Claude we should have the return_json option provide more detailed info. Another case of this is Claude often tried the help command, but the return value does not include the text of the help page so I don't think Claude got much out of it.

[Eric Pettersen]

It seems like this would need to be wedged into "info chains" somehow, since the "open" command only knows about models, not chains, and doesn't ask for JSON info for the models. I mean it could do that, the atomic model could include then include the UniProt info , but realistically it should put in a lot more info than just the UniProt chain annotations, which would duplicate much of the effort already put into the "info" command.

Specifically, "info chains /a attr features" almost gets you there now, but Sequence.features is a method. Some property for getting UniProt annotations would need to be added, that in turn calls Sequence.features(...)