Add NanoBio toxicity estimator tool (nanoparticle preclinical screening)

[ghasn43]

Summary

This PR adds a new NanoBio tool module under src/tooluniverse/tools/nanobio/:

• nanobio_toxicity_estimator: deterministic, early-stage nanoparticle toxicity risk estimation from size (nm), surface charge (mV), and material.

Motivation

NanoBio tools aim to support agentic scientific workflows by providing structured, auditable utilities for nanomedicine research. This first tool is intended as a lightweight baseline for preclinical screening and educational/research use.

Tool Details

• Tool name: nanobio_toxicity_estimator
• Inputs: size_nm, charge_mV, material
• Outputs: toxicity_score (0–10), risk_level, reasons, confidence, success
• Deterministic: yes (no randomness)

Notes / Safety

This tool is intended for research and preclinical screening only and is not a clinical decision-making system.

Author

Ghassan Muammar (Experts Group FZE)

[ghasn43]

Dear Tools Universe Team,

I hope this message finds you well.

I am writing to kindly follow up on a request I submitted via the Harvard Tools Universe platform over a month ago. As of today, I have not yet seen any update or response, and I wanted to check whether the request was received successfully or if any additional information is required from my side.

I fully understand that requests may take time to review, especially given the volume you may be handling. However, I would greatly appreciate it if you could kindly look into the status of my submission when possible, or advise on the expected timeline.

Thank you very much for your time and support. I look forward to your guidance.

Kind regards,
Ghassan Muammar

[gasvn]

Hi, thank you for contributing to ToolUniverse! The estimator currently appears to use a simple heuristic with fixed thresholds and confidence levels. Is this intended to be a demo or example tool?

We are looking to accept tools that are suitable for general use. If this is a specialized tool on a special case, we suggest implementing it locally instead.