Skip to main content
Glama
huangjianhuster

Biomolecule Modeling MCP Server

relax_pdb_structure

Energy-minimize and optionally run short restrained molecular dynamics on a prepared PDB to eliminate clashes and produce a relaxed structure ready for production simulations.

Instructions

Energy-minimise and optionally run short restrained MD on a prepared PDB.

WHEN TO USE

Use as the FINAL step after fix_pdb_structure (and optionally assemble_pdb_structures). The input MUST have hydrogens and standard residue names — run fix_pdb_structure first.

Do NOT pass a raw PDB straight to this tool. OpenMM will fail if residues are missing heavy atoms or contain non-standard residue names.

WORKFLOW POSITION

Last step of the cleaning/preparation pipeline. Output is a relaxed PDB ready for production MD setup or coarse-graining.

DECISION GUIDANCE

preset (default "amber14_implicit"): amber14_implicit — use for typical protein relaxation; fast, no periodic box required. Best choice for most users. amber14_explicit — use when the input already has a periodic solvent box (added externally). More accurate but slower. amber99sb_implicit — an older force field; prefer amber14_implicit unless the user specifically requests AMBER99SB. charmm36_explicit — use when downstream simulation will use CHARMM36 and explicit solvent. Call query_ff_presets() to see the full list with descriptions.

run_md (default True): Set False for a minimisation-only run, which is much faster. Use minimisation-only when: (a) the structure is already well-relaxed, (b) a quick clash-removal pass is all that is needed, or (c) compute time is limited.

restrain_backbone (default True): Keep True unless the user wants full unrestrained relaxation. Backbone restraints preserve the experimental fold; without them a very short MD run can distort secondary structure.

restraint_k (default 1000 kJ/mol/nm²): Reduce to 100–200 for softer restraints that allow more backbone movement. Increase to 5000 for near-rigid backbone relaxation of side-chains only.

production_steps (default 25 000 ≈ 100 ps at 4 fs): Sufficient for side-chain relaxation and removal of clashes introduced by adding missing atoms. Increase to 250 000 (1 ns) for more thorough equilibration — note this takes substantially longer on CPU.

temperature (default 300 K): Use 300 K for room-temperature simulation. Some crystallographers prefer 277 K to match cryo conditions.

OUTPUT — WHAT TO CHECK

energy_initial_kJ_mol vs energy_final_kJ_mol: A drop of 10³–10⁶ kJ/mol after minimisation is normal for a raw crystal structure. If the final energy is still very large (> −10 000 kJ/mol for a 500-residue protein), the structure may have unresolved clashes — report to the user and suggest checking with query_pdb_structure. energy_post_md_kJ_mol: Should be more negative than energy_post_min_kJ_mol. If it is more positive, MD is diverging — reduce production_steps or timestep.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoRecord key decisions, e.g. "using implicit solvent for speed; run_md=False as structure only needed clash removal before coarse-graining".
presetNoForce-field preset (default "amber14_implicit").amber14_implicit
run_mdNoRun MD after minimisation (default True).
minimizeNoRun initial energy minimisation (default True).
input_pdbYesPrepared PDB with hydrogens and standard residues.
output_pdbNoOutput path (default: <stem>_relaxed.pdb).
restraint_kNoBackbone spring constant kJ/mol/nm² (default 1000).
temperatureNoTarget temperature in K (default 300).
timestep_fsNoIntegration timestep in fs (default 4.0).
heating_stepsNoSteps for temperature ramp (default 5 000).
platform_nameNo"CUDA", "OpenCL", "CPU", or None for auto.
final_minimizeNoFinal minimisation after MD (default True).
heating_stagesNoNumber of temperature ramp stages (default 10).
save_minimizedNoSave post-initial-minimisation PDB (default True).
report_intervalNoLog every N steps (default 1 000).
production_stepsNoSteps at target temperature (default 25 000).
minimize_max_iterNoMax minimisation steps; 0 = until convergence.
restrain_backboneNoRestrain CA/N/C/O during MD (default True).
heating_start_tempNoStarting temperature in K (default 10).
minimize_toleranceNoConvergence criterion kJ/mol/nm (default 10.0).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries the full transparency burden and does so thoroughly. It discloses failure modes (OpenMM will fail on missing atoms/non-standard residues), explains expected energy drops, flags signs of MD divergence, and describes output readiness.

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 well-structured into clear sections: WHEN TO USE, WORKFLOW POSITION, DECISION GUIDANCE, and OUTPUT. Each paragraph serves a distinct purpose and provides actionable information, so the length is justified for a 20-parameter scientific tool.

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?

Given the tool's complexity, no annotations, and an output schema, the description covers prerequisites, workflow position, detailed parameter selection, and output validation checks. It gives the agent enough context to invoke the tool correctly and interpret results, making it effectively complete.

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?

The schema covers 100% of parameters, so baseline is 3. The description adds substantial meaning for key parameters like preset, run_md, restrain_backbone, restraint_k, production_steps, and temperature with concrete numeric values and decision rules, elevating it above baseline. It does not discuss every parameter but is not required to given schema coverage.

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 description states a specific action: 'Energy-minimise and optionally run short restrained MD on a prepared PDB.' It clearly identifies the resource (a prepared PDB), the operation (energy minimisation and optional MD), and distinguishes itself as the final pipeline step after fix_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?

The description provides explicit WHEN TO USE guidance, positions the tool in the workflow, and warns against passing raw PDBs. It also includes per-preset decision guidance and conditions for setting run_md=False, making alternatives and exclusions clear.

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