Skip to main content
Glama

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

NameRequiredDescriptionDefault
stepsNoNumber of dilution tubes to generate.
seriesNameNoName for the dilution series.
volumeUnitNoVolume unit for transfer, diluent, and final tube volumes.
finalVolumeNoFinal volume in each tube.
dilutionFactorNoConstant dilution factor applied at each dilution step.
concentrationUnitNoUnit for stock and calculated final concentrations.
stockConcentrationNoStarting stock concentration before the first dilution.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the tool is purely a planner returning computed volumes and concentrations, but says nothing further about constraints (e.g., the 12-step ceiling) or validation behavior beyond what the schema states.

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?

Two sentences, with the usage trigger front-loaded before the explanation of outputs. The trailing enumeration of inputs largely restates the schema, which is mild redundancy but not damaging.

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 a full input schema, an output schema, and rich annotations, the description needs only to convey purpose and scope, which it does. An agent has enough to invoke it correctly; only edge-case behavior at the step/unit limits is left unaddressed.

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 every parameter including enums and minimums is already documented in structured form. The description names four of the seven inputs (stock concentration, dilution factor, tube count, final volume) but adds no semantics beyond the schema; baseline 3 applies.

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 transfer and diluent volume per tube and the resulting concentration at each step") and scopes it to serial dilutions, so an agent knows exactly what it computes. It does not explicitly contrast with adjacent siblings like solution_prep or pcr_master_mix, 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 Guidelines4/5

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

"Use for any serial dilution (standard curves, titrations, dose series)" gives a clear activation condition with concrete scenario examples. There are no exclusions or named alternatives, so an agent is not told when a different planning tool would be the better pick.

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