Skip to main content
Glama
huangjianhuster

Biomolecule Modeling MCP Server

fix_pdb_structure

Corrects common PDB structural errors—missing atoms, nonstandard residues, unwanted heterogens—and adds hydrogens to prepare files for OpenMM simulation.

Instructions

Prepare a PDB file for OpenMM by correcting common structural problems.

WHEN TO USE

Run this after query_pdb_structure (and optionally split_pdb) and before relax_pdb_structure. It is required before relaxation because OpenMM needs: (a) standard residue names, (b) all heavy atoms present, (c) hydrogen atoms added.

WORKFLOW POSITION

Step 3 (or step 2 if no splitting is needed). Input is typically the raw PDB or the protein-only file produced by split_pdb.

DECISION GUIDANCE

chains_to_keep / chains_to_remove: Decide based on query_pdb_structure output. For a standard relaxation workflow keep only the biological unit (usually protein chains). Remove chains that are crystallographic symmetry mates or that lack force-field parameters.

ph (default 7.0): Controls protonation states of HIS, ASP, GLU, LYS, CYS. Use 7.4 for physiological simulation. Use the experimental pH if known from the paper. Histidine protonation is particularly sensitive — consider whether HID/HIE/HIP matters for your system.

remove_heterogens (default True): Set False only if ligands have been separately parameterised and the assembled structure is ready for a non-standard force field. For standard AMBER/CHARMM relaxation, ligands without parameters will cause createSystem() to fail.

keep_water (default False): Set True only when crystallographic waters are meaningful (e.g. active-site waters). Waters slow minimisation and are usually re-added during explicit-solvent solvation later.

fix_missing_residues (default False): Only enable for gaps ≤ ~5 residues or when the user explicitly requests loop modelling. Modelled loops have roughly-placed atoms and require extensive MD to be meaningful. Large gaps (> 10 residues) will produce severe clashes and should be left open.

fix_terminal_residues (default False): Disordered termini are almost never worth modelling; leave False unless specifically requested.

OUTPUT — WHAT TO CHECK

nonstandard_residues: List what was converted. Flag any unexpected conversions to the user (e.g. a bound cofactor being converted to a standard amino acid). missing_atoms_added: Review side-chains added. A large number (> 20) suggests significant disorder in the crystal structure. heterogens_removed: If this is 0 when ligands were present, something was misclassified — re-check with query_pdb_structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phNopH for protonation assignment (default 7.0).
notesNoRecord key decisions, e.g. "keeping only chain A, pH 7.4 for physiological simulation, not modelling 22-residue loop as it is far from the active site".
input_pdbYesPath to input PDB or mmCIF file.
keep_waterNoPreserve crystallographic waters when removing heterogens (default False).
output_pdbNoOutput path (default: <stem>_fixed.pdb).
add_hydrogensNoAdd H atoms at the given pH (default True).
chains_to_keepNoRetain only these chain IDs.
chains_to_removeNoRemove these chain IDs.
remove_heterogensNoRemove ligands and ions (default True).
fix_missing_residuesNoModel missing internal loops (default False; requires SEQRES records).
fix_terminal_residuesNoAlso model missing terminal residues (default False; only with fix_missing_residues=True).
add_missing_heavy_atomsNoAdd absent side-chain heavy atoms (default True).
replace_nonstandard_residuesNoMap modified residues to standard ones (default True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It discloses key behaviors: adding hydrogens, adding missing heavy atoms, mapping nonstandard residues, removing heterogens, and modeling missing residues/termini with associated risks. It also explains consequences like clashes from large loop gaps and slow minimization with water. It could be slightly more explicit about whether the input file is modified or a new output file is written, but the output_pdb parameter and output-check section imply this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but exceptionally well-structured with clear headers (WHEN TO USE, WORKFLOW POSITION, DECISION GUIDANCE, OUTPUT). Every sentence has a purpose and front-loads the most critical workflow information. Despite its length, it remains scannable and directly actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 13 parameters, the description is remarkably complete: it gives workflow position, parameter decision rules, and output interpretation guidance. The output-check section even tells the agent what anomalies to flag (e.g., unexpected nonstandard conversions, many missing atoms, zero heterogens removed when ligands were present). This covers both correct invocation and downstream validation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema by explaining semantic choices for chains_to_keep/remove, ph, remove_heterogens, keep_water, fix_missing_residues, and fix_terminal_residues. It does not add extra color for every parameter, but the schema already handles those well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line clearly states the tool's purpose: 'Prepare a PDB file for OpenMM by correcting common structural problems.' This specifies the verb, resource, and intended context. It also distinguishes itself from siblings by placing itself in the workflow between query_pdb_structure/split_pdb and relax_pdb_structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'WHEN TO USE' section directs the agent to run this after query_pdb_structure and before relax_pdb_structure, and states it is required before relaxation. It also gives decision guidance per parameter, explaining when to adjust chains, pH, heterogen removal, water, and missing-residue modeling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/huangjianhuster/biomolecule-modeling-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server