Skip to main content
Glama

analyze_flow_cytometry_ploidy

Read-only

flowPloidy's DNA-content (cell cycle, genome size) fit on one channel of a project FCS file, optionally one population: G1/G2 Gaussians per sample, broadened-rectangle S phase, debris and aggregates by bounded nlsLM; nuclei counts, G1 CVs, G2/G1 linearity, reduced chi-square; with a standard, the ratio and pg; without G2, the endoreduplication index.

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

Input Schema

NameRequiredDescriptionDefault
g2Nomodel G2 peaks; off for endopolyploid tissue (then the endoreduplication index is reported).
_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.
debrisNothe debris model. Values: SC (single cut), MC (multiple cut).SC
gatingNoa Gating-ML or FlowJo .wsp in the project; empty for none.
channelNothe DNA-content 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.
standardNowhich sample's G1 is the internal standard (a: lower G1, b: higher); empty for none.
trim_rawNodrop channel values at or above this (0 keeps every value).
linearityNothe G2/G1 ratio: fitted between 1.5 and 2.5, or held at 2. Values: variable (fitted), fixed (fixed at 2).variable
populationNoa population of the strategy to analyse (flowPloidy gate); empty for every event.
compensationNoas analyze_flow_cytometry.auto
debris_limitNopeaks below this bin are not used as starting peaks.
standard_sizeNothe standard's DNA content in pg (0 for none).
histogram_binsNohistogram bins.
samples_in_tubeNohow many samples (sets of G1/G2/S peaks) the model may hold.
compensation_methodNoas analyze_flow_cytometry.flowkit

Output Schema

NameRequiredDescriptionDefault
fitYesthe fitted parameters by name, stop code, iterations, nuclei counts per component, G1 CVs and the reduced chi-square; null when refused
refusedYesflowPloidy's refusal, or null
summaryYesratio to the standard, DNA content (pg) and endoreduplication index, each null when it does not apply
histogramYescounts per bin, events outside the population, the fitted bins, and the starting peaks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / refused / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

The description discloses a great deal beyond the annotations: the fitted model components (G1/G2 Gaussians per sample, broadened-rectangle S phase, bounded nlsLM debris/aggregates), and the reported quantities (nuclei counts, G1 CVs, G2/G1 linearity, reduced chi-square, ratio/pg with a standard). Since readOnlyHint and destructiveHint=false already cover the safety profile, this added modeling context is a real contribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, which is good, but the whole definition is one semicolon-chained sentence packed with jargon and nested clauses. It is efficient in length yet hard to parse, and a short second sentence handling usage or the standard/G2 trade-off would improve scanability without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter tool with nested objects and an output schema, the description covers the statistical model and outputs well and annotations cover safety. However, several parameters are dismissed as 'as analyze_flow_cytometry' (derived, compensation, compensation_method), forcing the agent to consult a sibling definition, and the project/file-selection mechanics are left entirely to the schema.

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 schema baseline is 3, but the description adds genuine meaning by linking parameters to outcomes: enabling a standard yields the ratio and pg value, disabling g2 yields the endoreduplication index, and a population restricts the fit to one gate. This explains the consequences of key choices rather than repeating field text.

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?

Names a specific verb and resource: a flowPloidy DNA-content (cell cycle, genome size) fit on one channel of a project FCS file, with the model spelled out (G1/G2 Gaussians, S phase, debris/aggregate terms via nlsLM). This clearly separates it from the generic analyze_flow_cytometry sibling, though it never states the distinction explicitly.

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 context is implied by the topic (ploidy/genome-size estimation on a single DNA channel) and by conditional statements such as 'with a standard, the ratio and pg' and 'without G2, the endoreduplication index'. There is no explicit when-to-use versus when-not guidance and no named alternative, so the agent must infer that this is the specialized ploidy path rather than the general cytometry analysis.

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