← Tamarind BioCONTENT HISTORY

Update to Tamarind Bio

Snapshot Sep 30, 2026 · 22:50 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "tamarind-mcp-docking",
  "description": "Dock or screen known ligands against a receptor, perform protein-protein docking, or score existing poses and complexes with Tamarind Bio through MCP. Use for pocket-based or blind docking and pose ranking. Not for sequence co-folding, generating a new ligand or binder, or general structure prediction.",
  "included_files": [],
  "skill_md_contents": "---\nname: tamarind-mcp-docking\ndescription: Dock or screen known ligands against a receptor, perform protein-protein docking, or score existing poses and complexes with Tamarind Bio through MCP. Use for pocket-based or blind docking and pose ranking. Not for sequence co-folding, generating a new ligand or binder, or general structure prediction.\n---\n\n# Dock and score through MCP\n\nStart from the input the user actually has: receptor structure, ligand or SMILES/library, known pocket box, or an existing complex.\n\n## Select the method\n\nCall `listTags` when needed, then query `getAvailableTools` for protein-ligand docking, protein-protein docking, or binding affinity. Inspect the exact candidate with `getJobSchema`.\n\n- Prefer box-based physics docking when pocket coordinates are known.\n- Prefer blind methods only when the live schema supports the available inputs.\n- Prefer score-only tools for a pose or complex that already exists.\n- Fold sequence-only inputs before sending them to structure-only docking fields.\n\nClosely related tools use different receptor, ligand, box, exhaustiveness, and scoring fields. Never transfer a sibling payload without schema inspection.\n\n## Prepare and run\n\nUpload receptor or ligand files with `uploadFile`, or use exact accepted `s3Path` values from successful upstream jobs. Keep receptor and ligand separate when required.\n\nCall `validateJob` and `estimateTime`. Confirm blind versus box docking, pocket definition, ligand count, pose count, exhaustiveness or sampling, rescoring, and estimated spend. Route a library to `tamarind-mcp-batch` or a schema-supported file batch instead of looping `submitJob`.\n\nUse `tamarind-mcp-submit-and-poll`. Retrieve poses and score tables by calling `listJobFiles` before targeted `getJobFile` calls.\n\nReport whether lower energy/affinity or higher model confidence is better. Check pose geometry and interactions; docking scores prioritize candidates but do not prove experimental binding.\n"
}

SHA-256: f409794ff828b9aecad4f55c82b1b197f467eeaffb2ca3d651e2a354a9cb91c5