chamaileon_design_binder_multi – 1 MCP server offers this tool

What it usually takes

  • binder_len – in 1 of 1
  • hotspot1_str – in 1 of 1
  • hotspot2_str – in 1 of 1
  • num_timesteps – in 1 of 1
  • pdb1_file – in 1 of 1
  • pdb2_file – in 1 of 1
  • seed – in 1 of 1
  • target1_choice – in 1 of 1
  • target2_choice – in 1 of 1

No server marks it as only reading: treat it as able to change data.

From each publisher's own tool list. We never call a tool.

Servers

ServerInputsRead-only?
Chamaileon co.huggingface.hugging-apps/chamaileon Design one binder that binds two different target contexts. If a user passes a file as an input, use the upload_file_to_gradio tool, if present, to upload the file to the gradio app and create a Gradio File Input. Then use the returned path as the input to the tool. Returns: (binder sequence, complex 1 PDB, complex 2 PDB, status text)binder_len,hotspot1_str,hotspot2_str,num_timesteps,pdb1_file,pdb2_file,seed,target1_choice,target2_choiceNot stated