Skip to main content
Glama

fit_flow_cytometry_compass

Read-only

COMPASS polyfunctionality on a project CSV of Boolean cytokine-subset counts (FlowJo export), stimulated and unstimulated rows paired by subject: each subject's posterior probability of response per subset, and functionality and polyfunctionality scores.

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

Input Schema

NameRequiredDescriptionDefault
groupNoa column to group scores by; empty for none.
_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.
subjectNothe subject column.
_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.
conditionNothe condition column.
mcmc_seedNothe R seed.
iterationsNoiterations per pass.
stimulatedNoits stimulated value.
count_tableNothe project count CSV.
replicationsNosampling passes.
unstimulatedNoits unstimulated value.
min_stimulatedNodrop subsets with fewer stimulated cells in all (0 keeps all).

Output Schema

NameRequiredDescriptionDefault
scoresYesper subject: group, functionality and polyfunctionality score
mean_gammaYessubsets and, per subject, the posterior probability of response in each

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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 safety is covered. The description adds real behavioral context beyond that: the required stimulated/unstimulated pairing per subject and the fact that the model produces per-subject posterior response probabilities plus functionality and polyfunctionality scores. It does not mention the MCMC iteration or replication cost, which is a minor gap.

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

Conciseness5/5

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

A single tightly packed sentence that front-loads the method and data format, then lists the outputs after a colon. No filler or duplicated schema content.

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 a 12-parameter statistical fitting tool with nested objects and an output schema, the description covers the essential data contract and return semantics, which is adequate. It leaves the sampling controls (iterations, replications, mcmc_seed) and the filtering parameter unmentioned at the narrative level, relying entirely on the schema.

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 does clarify what the count_table file should contain and what the stimulated/unstimulated columns represent, but it says nothing about subject, condition, group, iterations, replications or mcmc_seed beyond what 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 description names a specific method and resource: fitting a COMPASS polyfunctionality model to a project CSV of Boolean cytokine-subset counts from a FlowJo export. The term 'COMPASS polyfunctionality' distinguishes it from the proliferation, ploidy and gating siblings, though no sibling is named 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 is implied through data prerequisites rather than stated: the input must be a Boolean cytokine-subset count CSV with stimulated and unstimulated rows paired by subject. There is no explicit when-to-use, when-not, or pointer to an alternative fit tool such as fit_flow_cytometry_proliferation.

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