Update to Physical Validation

{
  "description": "Prepare or submit a Physical Validation experiment request for peptides, rabbits, mice, genes and plasmids, proteins and antibodies, sequencing, or other research work. Use when a person wants to specify work or send a sourcing request.",
  "included_files": [],
  "name": "prepare-experiment-request",
  "skill_md_contents": "---\nname: prepare-experiment-request\ndescription: Prepare or submit a Physical Validation experiment request for peptides, rabbits, mice, genes and plasmids, proteins and antibodies, sequencing, or other research work. Use when a person wants to specify work or send a sourcing request.\n---\n\nUse the connector's current request-tool schemas for field names, supported options, and validation. Account submissions require the host's managed OAuth connection. If sign-in is required, use the host's connection flow before calling an account tool.\n\n1. Select one service family for each request. The supported families are peptides, rabbits, mice, genes and plasmids, proteins and antibodies, sequencing, and other work described in a brief. Preserve the person's scientific specifications, requested outputs, quantities, materials, location, timeline, and provider choices. Ask about missing required answers without inventing sequences, animal details, legal entity information, or budget currency. Treat supporting constructs or cohorts as inputs only when the person explicitly links them to the selected work.\n2. For preparation or browser review, call `prepare_request` with the supplied information. It returns a review link containing the supplied fields and does not save an account draft or submit a request. Share that link with the person who requested it, taking account of any personal details it contains. For files that need uploading, use the browser request page because MCP accepts inline specifications.\n3. For submission, show the complete requested work and contact details, and obtain the person's explicit agreement to submit and to the service terms and privacy notice. Existing explicit authorization for that complete request is sufficient. Authenticate through the host and call `submit_request` with exactly one supported payload form. For an existing saved draft, read it first and use its current ID and revision.\n4. Keep the same idempotency key when retrying an unchanged submission. If a response is interrupted, preserve the payload and key. Report an uncertain outcome honestly and avoid a fresh submission key that could duplicate the request. Resolve validation errors from the returned field details, and obtain agreement again if the substantive request changes.\n5. Report submission only after the tool returns a successful receipt. Halmos reviews submitted requests before any supplier outreach. A submission receipt establishes intake, not supplier acceptance or work starting. Use only receipt links and facts returned by the service.\n\nService terms and privacy are available at https://physicalvalidation.com/terms and https://physicalvalidation.com/privacy.\n"
}