Skip to main content
Glama

LNP formulation (lipid nanoparticles)

lnp_formulation
Read-onlyIdempotent

Plan a lipid nanoparticle (LNP) formulation for RNA: from RNA mass, N/P ratio and lipid mol% (e.g. ionizable lipid/DSPC/cholesterol/PEG-lipid 50/10/38.5/1.5), calculate moles, mass and stock volume of every lipid, the ethanol and aqueous phase volumes at the chosen mixing ratio (default 3:1), and final RNA concentration, ethanol fraction and lipid:RNA ratio. Molecular weights must come from the user or certificates of analysis.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lnp_formulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
lipidsNoEvery lipid in the formulation; mol% must add up to 100 and exactly one is the ionizable lipid.
npRatioNoMolar ratio of ionizable-lipid amines (N) to RNA phosphates (P).
rnaMassNoMass of RNA (mRNA, siRNA, sgRNA) to encapsulate.
rnaMassUnitNoug
rnaStockUnitNomg/mL
aqueousVolumeNoVolume of the aqueous RNA phase.
formulationNameNo
aqueousVolumeUnitNouL
aqueousToEthanolRatioNoVolume ratio of aqueous (RNA) phase to ethanol (lipid) phase at mixing; 3 means 3:1.
rnaStockConcentrationNoConcentration of the RNA stock.
nucleotideMolecularWeightNoAverage mass per nucleotide used to estimate RNA phosphate (g/mol).

Output Schema

NameRequiredDescriptionDefault
cardNoWhat the Verbex card draws; same values as the notebook entry.
toolYes
resultNo
humanUrlNo
warningsNo
inputNotesNoHow the input was read when it was not in the documented shape. Tell the user.
safetyNotesNo
toolVersionNo
notebookEntryNoMarkdown entry to paste into a lab notebook.
validationErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / inputNotes
      Added value: +{
      +  "description": "How the input was read when it was not in the documented shape. Tell the user.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: it is a planning/calculation tool, the default mixing ratio is 3:1, and molecular weights must be supplied by the user or taken from certificates of analysis — a real input constraint an agent must know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that is front-loaded with the purpose and then lists outputs. It earns its length given the number of computed quantities, though the run-on structure makes it slightly harder to scan than a short bulleted list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description nonetheless previews them. For an 11-parameter, zero-required-parameter calculator, the main residual gap is that it never states the minimum viable input combination — an agent still has to infer whether rnaMass alone or rnaStockConcentration plus aqueousVolume is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 64% schema description coverage, the schema carries most parameter meaning. The description reinforces the conceptual chain (RNA mass + N/P + mol% -> moles, mass, stock volumes) and flags where molecular weights come from, but it does not clarify the relationship between rnaMass, aqueousVolume and rnaStockConcentration, nor nucleotideMolecularWeight or aminesPerMolecule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Plan a lipid nanoparticle (LNP) formulation for RNA') and then enumerates exactly what is computed: lipid moles/mass/stock volume, ethanol and aqueous phase volumes, final RNA concentration, ethanol fraction and lipid:RNA ratio. This is clearly distinct from siblings like solution_prep or serial_dilution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is the tool for LNP/RNA formulation planning driven by RNA mass, N/P ratio and lipid mol%. It does not name an alternative or state when NOT to use it (e.g. simple buffer prep), so it stops short of explicit routing, but the domain is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources