Skip to main content
Glama

export_flow_cytometry_population

Read-only

One population's events as a file: FCS 3.1 (FlowIO create_fcs, returned as base64) or CSV (returned as text).

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

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.
formatNothe file format. Values: fcs (FCS 3.1), csv (CSV).fcs
gatingNoa Gating-ML or FlowJo .wsp in the project; empty for none.
valuesNoacquired values with the spillover keyword, or the compensated values. Values: raw (as acquired), compensated (compensated).raw
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.
computedNoalso write the run's derived and unmixed channels.
documentNothe FCS file in the project, by name or id.
populationNothe population to write, by its gate id; empty for every event.
compensationNoas analyze_flow_cytometry.auto
compensation_methodNoas analyze_flow_cytometry.flowkit

Output Schema

NameRequiredDescriptionDefault
fileYesthe file: its name, MIME type, event count, and the CSV text or the FCS bytes as base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral detail the annotations do not: the return payload differs by format (base64 blob for FCS, plain text for CSV), which is important for downstream handling. It stops short of saying whether anything is written into the project or how large exports behave.

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?

A single front-loaded sentence with no filler and no redundancy, and the format-to-encoding mapping is packed efficiently. It is arguably over-compressed for an eleven-parameter tool, but nothing in the text is wasteful.

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 input schema is fully documented, which lowers the burden, but with 11 parameters, a nested _subject object, and gating/compensation interplay, the one-sentence description leaves the agent without orientation on the core inputs (document, population) or their dependencies. Adequate as a pointer, thin as an explanation.

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 baseline is 3; the description only echoes the 'format' parameter's semantics by explaining what fcs and csv produce. It adds no meaning for the remaining ten parameters (gating, values, compensation, derived, document, population, computed), which the schema already documents.

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 sentence names the resource precisely ('One population's events as a file') and enumerates the two supported output formats with their encodings (FCS 3.1 via FlowIO create_fcs as base64, CSV as text). It is clear this is a per-population export/conversion tool, though it never names the source document it exports from, so the actor-side of the operation is only implied.

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?

There is no when-to-use guidance at all: nothing tells the agent to prefer this over analyze_flow_cytometry or batch_flow_cytometry, nor when FCS is the right choice versus CSV beyond restating the formats. No prerequisites (gating, compensation) or selection conditions are offered, leaving routing entirely to inference.

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