Skip to main content
Glama

estimate_spectra_from_controls

Read-only

flowSpecs specMatCalc on spectral single-stain control tubes in the project: per tube, MAD gates on scatter and the brightest detector, the median of every detector; each group's dimmest tube subtracted, autofluorescence added, each signature scaled to its maximum.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tubes": "<tubes>",
      "groups": "<groups>",
      "autofluorescence": "<autofluorescence>"
    },
    "name": "estimate_spectra_from_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
tubesYesthe control FCS files in the project, by name or id, comma-separated, the unstained and autofluorescence tubes included.
_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.
groupsYesthe tube-name prefixes that group tubes acquired alike, comma-separated (Beads_, Dead_).
_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.
excludedNoregular expression for the channels that are not detectors.Time|SC|Sort|ate|omp|LightLoss|Row|Column
autofluorescenceYeswhich of the tubes is the unstained one whose spectrum is the autofluorescence, by name or id.

Output Schema

NameRequiredDescriptionDefault
tubesYeswhat each tube's gates kept, its brightest detector and its role
matrixYesthe spectral matrix, rows the fluorochromes, columns the detectors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds useful process detail beyond that: MAD gating on scatter and the brightest detector, per-detector medians, dimmest-tube subtraction, autofluorescence addition, and per-signature max scaling. It does not disclose failure behaviour (e.g. what happens when gating rejects a tube) or computational cost.

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?

It is a single dense sentence with no wasted words, but it is packed with R-package jargon (flowSpecs, specMatCalc) and a run-on list of algorithm steps. It is compact yet not front-loaded with a plain statement of what the tool returns.

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, so return values need not be described. However, for a six-parameter tool with nested objects and a same-purpose sibling, the description omits the crucial disambiguation from estimate_spillover_from_controls and prerequisites about control-tube composition, leaving a real gap.

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 schema already explains every parameter, making 3 the baseline. The description adds only a little semantic linkage, showing that groups drive the dimmest-tube subtraction and that the autofluorescence value is added per group, which slightly clarifies how the two required inputs interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (spectral single-stain control tubes in the project) and gestures at the operation via 'flowSpecs specMatCalc', but it never states in plain terms that the tool estimates per-detector spectra. It also does not distinguish the output from the sibling estimate_spillover_from_controls, which is the obvious near-neighbour an agent must choose between.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the sibling spillover tool as the alternative. The only implied usage comes from the input descriptions (tubes must include unstained and autofluorescence tubes), not from the description itself.

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