← 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-developability",
  "description": "Score protein or antibody candidates for stability, aggregation, solubility, viscosity, polyreactivity, glycosylation, immunogenicity, and related developability risks with Tamarind Bio through MCP. Use as a post-design filter. Not for generating molecules, folding structures, or measuring binding alone.",
  "included_files": [],
  "skill_md_contents": "---\nname: tamarind-mcp-developability\ndescription: Score protein or antibody candidates for stability, aggregation, solubility, viscosity, polyreactivity, glycosylation, immunogenicity, and related developability risks with Tamarind Bio through MCP. Use as a post-design filter. Not for generating molecules, folding structures, or measuring binding alone.\n---\n\n# Filter candidates for developability\n\nTreat developability as a panel of orthogonal risks, not one universal score.\n\n## Select the panel\n\nCall `listTags` to obtain current function values, then use filtered `getAvailableTools` calls for developability, stability, aggregation, solubility, immunogenicity, or another relevant axis. Inspect each selected tool with `getJobSchema`.\n\nMatch the input type and modality. Sequence-only, structure-based, paired-antibody, and nanobody-specific tools are not interchangeable.\n\nUpload structures with `uploadFile` or use an accepted prior-job `s3Path`. Call `validateJob` and `estimateTime` for each planned tool. For a candidate list, use `tamarind-mcp-batch` so one settings policy is applied consistently; validate every distinct conditional payload shape before multiplying the run.\n\n## Execute and interpret\n\nUse `tamarind-mcp-submit-and-poll` for a single candidate and `tamarind-mcp-batch` for many independent candidates.\n\nReport every risk axis separately with the tool, units, direction, and threshold rationale. Preserve a Pareto set when candidates trade affinity against solubility, stability, or immunogenicity. Computational predictions prioritize assays and formulation work; they do not replace them.\n"
}

SHA-256: 220e0a8de5651df0e06f24d719dd0ada07327aa073044b69ff21911dfcea7123