Skip to main content
Glama

PCR / qPCR master mix

pcr_master_mix
Read-onlyIdempotent

Use when someone sets up a PCR or qPCR reaction mix for several wells. Calculates volume of each component per reaction and for the whole mix with excess, with water filling the remaining volume. Give each component a stock and final concentration (molar, ng/µL, x buffer, %), an amount per reaction (e.g. 1.25 U polymerase from 5 U/µL, 10 ng template from ng/µL), or a fixed volume. Template can be added per well separately. Do not list water; it is calculated.

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

Input Schema

NameRequiredDescriptionDefault
reactionsNoNumber of reactions (wells), including controls.
componentsNoMaster mix components except water (water fills the remaining volume). Give each either a stock and final concentration (or amount per reaction), or a fixed volume per reaction.
reactionNameNoName for the master mix, e.g. 'IL-6 qPCR plate 2'.
excessPercentNoExtra master mix to cover pipetting loss, as a percent of the reactions.
reactionVolumeNoTotal volume of one reaction, including template.
templateVolumeNoTemplate volume added to each well separately (not in the master mix).
reactionVolumeUnitNouL
templateVolumeUnitNoDefaults to the reaction volume unit.

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.3/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive calculator, so the bar is lower. The description nonetheless adds real behavioral detail: water is auto-filled and must not be listed, excess is applied to the whole mix, and template is handled per well outside the mix. It does not describe validation failures or edge behavior, which keeps it at 4.

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?

It is front-loaded with the use case and then moves into specification modes and constraints without filler. The critical 'Do not list water' rule sits at the end rather than near the component instructions, which is a minor structural miss.

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 present, return values need no explanation, and the description covers the input contract and calculation semantics well. It is nearly complete for this tool's complexity, lacking only notes on validation errors or unit-mismatch handling.

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?

Schema coverage is 88%, so the schema already documents most parameters. The description still adds interpretive guidance the schema does not: components may be specified by stock+final concentration, by amount per reaction (e.g. 1.25 U from 5 U/µL), or by fixed volume, plus the rule that water is omitted and calculated.

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: calculating component volumes for a PCR/qPCR master mix across several wells, including per-reaction and whole-mix amounts with excess. This is clearly distinguishable from reagent-focused siblings such as solution_prep, serial_dilution, or parse_reagent_label.

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 when someone sets up a PCR or qPCR reaction mix for several wells' gives a concrete triggering context. It stops short of naming when not to use it or pointing at an alternative tool for single-reaction or non-PCR calculations, so it earns a 4 rather than a 5.

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