Skip to main content
Glama

plan_serial_dilution

Read-only

Plan a serial dilution: the same fold dilution repeated tube after tube from a stock, each tube made to one volume. Returns the transfer and diluent volumes for every step, each tube's concentration and cumulative dilution, and what each tube holds after giving its transfer to the next.

Input Schema

NameRequiredDescriptionDefault
foldNothe dilution at each step, as a fold (1:10 is 10).
stepsNohow many dilutions to make.
_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.
tube_volumeYesthe volume of each dilution after mixing (transfer plus diluent).
tube_volume_unitNothe unit of the tube volume.µL
stock_concentrationYesconcentration of the stock the series starts from.
stock_concentration_unitNothe unit of the stock concentration, which every tube is reported in.mM

Output Schema

NameRequiredDescriptionDefault
finalYesthe last tube's concentration, in the stock's unit
tubesYeseach tube: step, concentration, cumulative fold, volume left after its transfer
diluentYesdiluent in each tube, in the tube volume's unit
transferYesvolume moved into each tube, in the tube volume's unit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description provides rich behavioral context by explicitly listing the output components: 'transfer and diluent volumes for every step,' 'each tube's concentration and cumulative dilution,' and the contents of the next tube. This level of detail is critical for a planning/simulation tool.

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?

The description is a single, dense sentence. While it is highly informative, it is slightly long and dense, but every clause serves to define the operation or its complex output.

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

Completeness5/5

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

Given that the input schema is 100% covered and includes complex biological metadata, the description provides the necessary workflow context (what the results will show) to make this tool fully usable without requiring the agent to deduce the output format.

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

Parameters4/5

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

While the schema is 100% covered, the description enhances meaning by providing practical definitions for parameters like 'fold' (e.g., 1:10 is 10) and clarifying 'tube_volume' as the total post-mixing volume (transfer plus diluent).

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 precisely defines the action ('Plan a serial dilution') and the specific mathematical process ('the same fold dilution repeated tube after tube'), immediately distinguishing it from simple concentration calculations.

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

Usage Guidelines3/5

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

The tool is used for planning a series of dilutions from a stock. However, it provides no guidance on when *not* to use this tool, nor does it mention any alternative tools that handle similar workflows.

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