Skip to main content
Glama

synthesize_flow_cytometry

Read-only

What an FCS file supports before any question (dynamic synthesis): channel roles, the events at each channel's storable maximum, the logicle flowCore estimateLogicle fits to each fluorescence channel's instrument range, flowDensity deGate's density valleys per scaled channel, and every population's share of its parent with its exact (Clopper–Pearson, R binom.test) interval.

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

Input Schema

NameRequiredDescriptionDefault
ANoas analyze_flow_cytometry.
MNoas analyze_flow_cytometry.
TNoas analyze_flow_cytometry.
WNoas analyze_flow_cytometry.
scaleNoas analyze_flow_cytometry.logicle
_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.
lambdaNoλ of Box-Cox or linlog.
asinh_aNothe a in asinh(a + b·x) + c.
asinh_bNothe b in asinh(a + b·x) + c.
asinh_cNothe c in asinh(a + b·x) + c.
biexp_aNoflowCore biexponential a.
biexp_bNoflowCore biexponential b.
biexp_cNoflowCore biexponential c.
biexp_dNoflowCore biexponential d.
biexp_wNoflowCore biexponential w.
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.
cofactorNothe c in asinh(x / c).
documentNothe FCS file in the project, by name or id.
biex_widthNoas analyze_flow_cytometry.
conf_levelNothe confidence level of every population interval.
compensationNoas analyze_flow_cytometry.auto
biex_negativeNoas analyze_flow_cytometry.
compensation_methodNoas analyze_flow_cytometry.flowkit

Output Schema

NameRequiredDescriptionDefault
channelsYesper channel: role, events at maximum, the fitted logicle and the density valleys
populationsYesper population: count, % of parent and that share's exact interval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the results are dynamically synthesized rather than stored, and specific estimators (flowCore estimateLogicle, flowDensity deGate, R binom.test Clopper–Pearson) produce them, which tells the agent the numbers are deterministic and method-derived. It does not mention compute cost, latency, or failure modes on files with no fluorescence channels.

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 scope statement is front-loaded, which is good, but everything is delivered as one 50-word run-on sentence with five comma-chained clauses. It contains no filler, yet the list-form payload would be far easier to scan as separate lines or bullets.

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?

An output schema exists and the description's job of explaining return content is therefore partly covered, and the enumeration of synthesized artifacts is genuinely helpful. However, for a tool with 25 parameters and many near-identical siblings, the description leaves out how this differs from analyze_flow_cytometry and what prerequisites (a loaded project, a resolved `document`) it needs.

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 description coverage is 100%, so the schema already documents all 25 parameters, including defaults and ranges. The description adds no parameter-level meaning, and most schema descriptions simply defer ('as analyze_flow_cytometry'), but the coverage baseline keeps this at 3 rather than lower.

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 names a specific verb (synthesize) and a specific resource (an FCS file's supported structure), then enumerates the concrete outputs: channel roles, storable-maximum events, logicle parameter fits, deGate density valleys, and per-population shares with Clopper–Pearson intervals. That is far more specific than a restatement of the name. It stops short of a 5 because it never explicitly contrasts itself with the sibling it repeatedly defers to, analyze_flow_cytometry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The phrase 'before any question' hints that this is a first-pass, pre-analysis synthesis, but no explicit when-to-use, when-not-to-use, or alternative is given. With a sibling named analyze_flow_cytometry invoked 6+ times for parameter meaning, the absence of a routing statement ('use this instead of / before that') is a real gap.

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