← Tamarind BioCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Tamarind Bio
Snapshot Sep 30, 2026 · 22:50 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "tamarind-mcp-antibody",
"description": "Design, redesign, model, number, humanize, or search antibodies, nanobodies, VHHs, and TCRs with Tamarind Bio through MCP. Use for CDR-aware and repertoire-specific workflows when MCP is requested. Not for generic non-antibody binder design, ordinary complex folding, or developability scoring alone.",
"included_files": [],
"skill_md_contents": "---\nname: tamarind-mcp-antibody\ndescription: Design, redesign, model, number, humanize, or search antibodies, nanobodies, VHHs, and TCRs with Tamarind Bio through MCP. Use for CDR-aware and repertoire-specific workflows when MCP is requested. Not for generic non-antibody binder design, ordinary complex folding, or developability scoring alone.\n---\n\n# Engineer antibodies through MCP\n\nClarify antibody versus VHH/nanobody/TCR and the goal: de novo CDR design, redesign, structure prediction, numbering, humanization, or repertoire/paratope search.\n\n## Select and inspect\n\nCall `getAvailableTools(modality=\"antibody\")`. Narrow with a live function such as antibody design or structure prediction, then call `getJobSchema` for the strongest fit.\n\nPrefer antibody-specific tools when chain pairing, CDR regions, framework numbering, epitope/hotspot steering, or humanization matters. Route generic co-folding to `tamarind-mcp-structure-prediction` and non-antibody binders to `tamarind-mcp-binder-design`.\n\n## Build and validate\n\nCapture the heavy/light or VHH sequence, framework, antigen structure and chain, epitope or hotspots, CDR regions and lengths, candidate count, and excluded residues required by the live schema. Upload structures with `uploadFile` and use the returned filename or an accepted prior-job `s3Path`.\n\nCall `validateJob`, require no mutation warning, and call `estimateTime`. Confirm chain identities, numbering scheme, CDR scope, candidate count, refolding plan, filters, and estimated spend before submission.\n\n## Execute and filter\n\nUse `tamarind-mcp-submit-and-poll`. For multiple independent candidates, use `tamarind-mcp-batch` rather than repeated `submitJob` calls.\n\nRank design outputs on interface confidence and geometry, then apply antibody-specific developability filters through `tamarind-mcp-developability`. Preserve sequence diversity and flag liabilities instead of selecting only the top scalar score. Predictions prioritize experiments; they do not replace binding and developability assays.\n"
}SHA-256: e8c744d12cccf4ba5fdb738d77430b42780df3c802d7c3324b3ddd153b736f7b