Update to Tamarind Bio

{
  "name": "tamarind-mcp-tool-discovery",
  "description": "Choose a Tamarind Bio tool by querying the live MCP catalog and schema. Use when the user requests MCP, has not named a tool, several tools could fit, or availability and required inputs must be verified. Not for reconnecting OAuth or executing a tool that is already selected.",
  "included_files": [],
  "skill_md_contents": "---\nname: tamarind-mcp-tool-discovery\ndescription: Choose a Tamarind Bio tool by querying the live MCP catalog and schema. Use when the user requests MCP, has not named a tool, several tools could fit, or availability and required inputs must be verified. Not for reconnecting OAuth or executing a tool that is already selected.\n---\n\n# Choose a live Tamarind tool\n\nNever recommend a tool from memory alone. The catalog is account-scoped and changes over time.\n\n## Narrow the catalog\n\n1. Identify the input already available: sequence, structure, receptor plus ligand, fixed backbone, labeled table, density map, or library.\n2. Identify the required output: structure, pose, affinity, designed sequence, generated molecule, embedding, property score, or ranked candidates.\n3. Call `listModalities` and `listTags` when the correct facet values are not known.\n4. Call `getAvailableTools` with `modality`, `function`, or a narrow `search`. Avoid an unfiltered catalog response.\n5. Inspect the strongest candidate with `getJobSchema(jobType=...)`.\n\nRecommend one primary tool and at most two conditional alternatives. Explain the input or scientific condition that changes the choice; avoid unsupported best-in-class claims.\n\n## Treat the schema as authority\n\nConfirm required fields, types, enum values, conditionals, defaults, file inputs, and account-visible variants. Do not copy settings between sibling models.\n\nFor a concrete proposed payload, call `validateJob` with a durable probe name. Require `valid: true` and no `mutatedFields` warning. Validation is free and does not authorize a paid run. If a file field fails because the file is absent, upload it with `uploadFile` or choose an exact `s3Path` from `listJobFiles`; do not guess a path.\n\nValidation checks schema and character constraints, not scientific identity. Confirm molecule type independently, especially when nucleotide letters could also be parsed as amino-acid codes.\n\n## Route execution\n\n- One known job: use the matching MCP domain skill plus `tamarind-mcp-submit-and-poll`.\n- One tool over many inputs: use `tamarind-mcp-batch`.\n- Dependent stages: use `tamarind-mcp-pipeline`.\n\nCompute trivial local properties locally when a standard library can answer them quickly. Reserve Tamarind for managed inference, durable artifacts, or platform workflows.\n"
}