Verbex Lab Tools

Serial dilution planner

serial_dilution

Read-onlyIdempotent

Use for any serial dilution (standard curves, titrations, dose series). Plans transfer and diluent volume per tube and the resulting concentration at each step, from a stock concentration, a constant dilution factor, the number of tubes and the final volume per tube.

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": "serial_dilution"
  }
}

Input Schema

Name	Required	Description
`steps`	No	Number of dilution tubes to generate.
`seriesName`	No	Name for the dilution series.
`volumeUnit`	No	Volume unit for transfer, diluent, and final tube volumes.
`finalVolume`	No	Final volume in each tube.
`dilutionFactor`	No	Constant dilution factor applied at each dilution step.
`concentrationUnit`	No	Unit for stock and calculated final concentrations.
`stockConcentration`	No	Starting stock concentration before the first dilution.

Output Schema

Name	Required	Description
`card`	No	What the Verbex card draws; same values as the notebook entry.
`tool`	Yes
`result`	No
`humanUrl`	No
`warnings`	No
`safetyNotes`	No
`toolVersion`	No
`notebookEntry`	No	Markdown entry to paste into a lab notebook.
`validationErrors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare this safe, read-only, idempotent, and closed-world, so the description doesn't need to repeat that. It does add that the tool computes per-tube transfer volume, diluent volume, and resulting concentration at each step, but leaves open computational details such as whether transfer volume is included in final volume.

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?

Two sentences, front-loaded with the usage trigger, followed by the output the tool plans. Nothing in it is redundant with the schema or annotations.

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?

With an output schema covering return values and full annotation coverage, the description only needs to convey scope and computed outputs, which it does. Slight gap: it doesn't mention the 12-tube cap that the schema enforces, which would matter for large dose series.

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 baseline is 3. The description restates four of the seven parameters (stock concentration, constant dilution factor, number of tubes, final volume per tube) and clarifies that the factor is applied uniformly at each step, but adds no syntax or unit-coupling 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 and resource (plans a serial dilution) and enumerates concrete applications (standard curves, titrations, dose series), which implicitly separates it from siblings like solution_prep or lnp_formulation. No explicit sibling comparison, so it stops short of a 5.

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?

"Use for any serial dilution" plus the parenthetical use cases gives clear triggering context for an agent deciding among sibling tools. It doesn't state when not to use it or name an alternative for one-off single dilutions.

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

All Verbex Lab Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?