Skip to main content
Glama

calibrate_flow_cytometry_beads

Read-only

flowBeads gateBeads on a calibration-bead FCS tube in the project and its lot's MEF table: every bead population (flowCore's default logicle, quantile-seeded R k-means per channel, the median label per event), each population's count, mean, SD and CV per channel, and for every certified channel the least-squares line trans(MEF) = alpha + beta * trans(MFI) with its residual standard error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tube": "<tube>",
      "mef": "<mef>"
    },
    "name": "calibrate_flow_cytometry_beads"
  }
}

Input Schema

NameRequiredDescriptionDefault
mefYesthe lot's MEF table in the project (';'-separated, the blank row first), by name or id.
tubeYesthe bead FCS file in the project, by name or id.
_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.

Output Schema

NameRequiredDescriptionDefault
mefYesper certified channel: alpha, beta and the residual standard error
statsYesper channel, per bead population: count, mean, SD, CV

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/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 the safety profile is covered. The description adds real behavioral context beyond that: the gating method (flowCore default logicle, quantile-seeded R k-means, median label per event) and the per-certified-channel regression reveal that results are deterministic and method-specific. It does not discuss failure modes, such as a tube that is not a bead tube or a lot with no certified channels.

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 tool's scope is front-loaded and every clause carries information (gating method, per-population statistics, per-channel regression). It is a single very dense sentence, however, and would read more cleanly split into what it computes versus how it gates; no filler is present.

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?

An output schema exists, so return values needn't be explained, yet the description still characterizes the main result categories. For a computation tool with full schema coverage and annotations, the remaining gap is operational: no mention of what happens with non-bead input, unmatched lots, or channels lacking certification.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: the tube must be a calibration-bead FCS file and the mef table must be that tube's lot MEF table, which communicates the required coupling between the two mandatory parameters. The _files/_subject plumbing is left entirely to the schema, which is appropriate.

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 names a specific verb (gate bead populations and fit a calibration line) on specific resources (a calibration-bead FCS tube plus its lot's MEF table) and enumerates the derived outputs (population counts, mean/SD/CV per channel, least-squares trans(MEF) = alpha + beta * trans(MFI) with residual SE). That specificity separates it from generic siblings such as analyze_flow_cytometry or estimate_flow_cytometry_scale, which don't mention bead gating or MEF calibration.

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?

Usage is implied rather than stated: the requirement for a calibration-bead tube and its matching lot MEF table tells the agent this is a bead-calibration step, but there is no explicit when-to-use versus when-not-to-use guidance and no named alternative (e.g., estimate_flow_cytometry_scale) for related scale work. The prerequisites are inferable from the parameter descriptions rather than the description text.

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