Skip to main content
Glama

Jean — Molecular Biology & Genomics

solve_dilution

Read-only

Solve C₁V₁ = C₂V₂ for whichever of the four quantities is left empty (stock concentration, stock volume, final concentration, final volume), each in its own unit: molar (M to fM), mass per volume (mg/mL to ng/mL), fold (X) or percent.

Input Schema

NameRequiredDescriptionDefault
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
final_volumeNofinal volume (V₂). Leave exactly one of the four quantities empty: that one is calculated.
stock_volumeNostock volume (V₁). Leave exactly one of the four quantities empty: that one is calculated.
final_volume_unitNothe unit of the final volume, given or solved.mL
stock_volume_unitNothe unit of the stock volume, given or solved.µL
final_concentrationNofinal concentration (C₂). Leave exactly one of the four quantities empty: that one is calculated.
stock_concentrationNostock concentration (C₁). Leave exactly one of the four quantities empty: that one is calculated.
final_concentration_unitNothe unit of the final concentration, given or solved.µM
stock_concentration_unitNothe unit of the stock concentration, given or solved.mM

Output Schema

NameRequiredDescriptionDefault
foldYesC₁/C₂, how many times the stock is diluted
unitYesthe solved quantity's unit
valueYesthe solved quantity, in its own unit
solvedYeswhich quantity was solved, by its parameter name
diluentYesV₂ − V₁, the diluent to add, in V₂'s unit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that the missing quantity is calculated and lists supported unit families, but it does not describe validation behavior (e.g., what happens with zero or multiple empty quantities) or output format.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; it states the equation, the four quantities, and the unit families efficiently.

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?

For a read-only calculator with an output schema and full parameter descriptions, the description covers the core calculation and units. It does not explain the unrelated _subject/_files project parameters, but those are documented in the schema and not central to the dilution operation.

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?

Schema description coverage is 100%, so the schema already documents each parameter and the 'leave exactly one empty' rule. The description reinforces the equation and unit categories but adds little syntax or constraint detail beyond the schema.

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

Purpose4/5

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

States a specific verb (solve) and the exact equation and four quantities, so the operation is unambiguous. It does not explicitly contrast with sibling tools such as plan_serial_dilution, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

The only usage instruction is to leave exactly one of the four quantities empty; that is parameter mechanics, not tool-selection guidance. It never says when to use this solver instead of plan_serial_dilution or convert_mass_moles.

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