Skip to main content
Glama

estimate_flow_cytometry_scale

Read-only

Choose the transform from the data. flowVS: the asinh(x / c) cofactor of one channel that makes its density peaks' variances most alike across project FCS files (Bartlett's statistic, Brent search over e^-1..e^10). flowTrans: the arcsinh, Box-Cox, linlog or biexponential parameters that make two or more channels of one file most jointly normal (profile likelihood, L-BFGS-B).

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

Input Schema

NameRequiredDescriptionDefault
modelNoflowtrans: the transform.arcsinh
_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.
gatingNoa Gating-ML or FlowJo .wsp in the project; empty for none.
channelNoflowvs: the channel.
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.
channelsNoflowtrans: two or more channels, comma-separated.
documentNothe FCS file in the project, by name or id.
estimatorNoflowvs or flowtrans.flowvs
populationNoa population, gated in every file; empty for all.
compensationNoas analyze_flow_cytometry.auto
sample_filesNoflowvs: project FCS files, comma-separated; empty for all.
compensation_methodNoas analyze_flow_cytometry.flowkit

Output Schema

NameRequiredDescriptionDefault
flowvsYesthe search (window optima, local cofactors) and each file’s peaks at the cofactor; null for flowTrans
cofactorYesflowVS's chosen cofactor, or null
flowtransYesthe fitted parameters, objective, convergence and the transform they define; null for flowVS
scale_paramsYesthe fit as analyze_flow_cytometry's `scale` and its parameters (flowVS: arcsinh and the cofactor), to display the data on it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 computational detail (Bartlett's statistic, Brent search over e^-1..e^10, profile likelihood, L-BFGS-B), which tells an agent the fitting is iterative and bounded, but says nothing about runtime cost, convergence failure behavior, or fallbacks. With annotations carrying the safety burden, 3 is appropriate.

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?

Front-loaded with the core action, then one sentence per estimator, so structure matches the two-mode interface. The statistical parentheticals (Bartlett's statistic, search bounds, L-BFGS-B) are dense but earn their place for selecting an estimator; a little trimming is possible.

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 need not be explained, and the description covers the conceptual core of both estimators. It leaves the seven bookkeeping parameters (gating, population, compensation, derived, _files, _subject, document) to 'as analyze_flow_cytometry' or the schema, which is acceptable but slightly thin for a 13-parameter tool.

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. The description nonetheless adds meaning beyond the terse schema strings: it ties channel to a single-channel variance criterion, channels to two-or-more jointly-normal fitting in one file, and sample_files to the cross-project file set, which clarifies what each parameter actually controls.

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?

The description states a specific verb and resource ('Choose the transform from the data') and immediately splits it into the two concrete modes (flowVS cofactor per channel; flowTrans multi-channel parameter set), so an agent knows this fits a transform-fitting task rather than gating or analysis. It does not explicitly distinguish itself from siblings such as analyze_flow_cytometry or calibrate_flow_cytometry_beads, which keeps it from 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 Guidelines3/5

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

Guidance is implicit in the mode split: one channel across project FCS files selects flowvs, two or more channels in a single file selects flowtrans. There is no explicit when-to-use versus alternatives, no prerequisites, and no statement of when neither mode applies, so usage must be inferred.

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