Skip to main content
Glama

fit_flow_cytometry_proliferation

Read-only

flowFit's division-dye model (CFSE, CellTrace, PKH26): a Gaussian fitted to a project file of unstimulated (parent) cells, then the stimulated file fitted by nls.lm as one Gaussian per generation a dye halving apart (position, width or spacing optionally held); each generation's %, flowFit's proliferation index and Roederer's indices.

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

Input Schema

NameRequiredDescriptionDefault
_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.
breaksNohistogram breaks.
gatingNoa Gating-ML or FlowJo .wsp in the project; empty for none.
channelNothe dye channel (PnN or PnS).
derivedNoas analyze_flow_cytometry.
_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.
documentNothe FCS file in the project, by name or id.
fix_sizeNohold the parent width.
populationNoa population, gated in both files; empty for all.
parent_fileNothe unstimulated (parent) FCS file.
compensationNoas analyze_flow_cytometry.auto
fix_distanceNohold the spacing at one dye halving.
fix_positionNohold the parent position.
smooth_windowNothe smoothing window.
compensation_methodNoas analyze_flow_cytometry.flowkit

Output Schema

NameRequiredDescriptionDefault
fitYesthe parent fit, the fitted and held parameters, spacing, iterations, deviance and the proliferation index; null when refused
indicesYesRoederer's division-tracking indices over flowFit's counts; null when refused
refusedYesflowFit's refusal, or null
generationsYesper generation: centre, rounded cell count and % of cells; null when refused

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a non-destructive, closed-world read, so the safety profile is covered. The description goes further by disclosing the actual computation — a Gaussian fitted to the parent, then nls.lm fitting one Gaussian per generation spaced a dye halving apart, with position/width/spacing optionally held — which is real behavioral context an agent cannot get from annotations.

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?

Dense but front-loaded — the model family and dye list come first, then the fitting method, then the outputs. It is a single semicolon-chained sentence with no filler, though the run-on structure and unexplained jargon (nls.lm, Roederer) cost some readability.

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?

For a 15-parameter tool with nested objects, the description covers the method, the two-input workflow, and what is produced (per-generation percentages, flowFit proliferation index, Roederer indices); an output schema exists so return values need not be detailed. Gaps are minor — no mention of gating/compensation prerequisites or failure modes when the model does not converge.

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 coverage is 100%, so the baseline is 3. The description does add meaning to the `fix_position`/`fix_size`/`fix_distance` trio by explaining that position, width or spacing may be held during the fit, and clarifies the parent-versus-stimulated file roles, but it says nothing about `breaks`, `smooth_window`, `gating`, or `compensation` beyond what the schema already states.

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 (fit) and a specific model (flowFit's division-dye model for CFSE/CellTrace/PKH26), with the two-file workflow spelled out. It is clearly distinguishable from `fit_flow_cytometry_compass` and generic `analyze_flow_cytometry` by naming the division-dye approach, though it never explicitly says which sibling to use instead.

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 description implies the usage context by describing the parent-then-stimulated fitting sequence, which tells an agent the required shape of input. However, there is no explicit 'use this when…' clause, no exclusion of the cell-cycle/Compass sibling, and no stated prerequisites such as needing both an unstimulated and a stimulated file.

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