Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_qpcr_delta_delta_ct

Calculate relative gene expression fold change from qPCR Ct values using the 2^(-ΔΔCt) method. Enter target and reference Ct values for treated and control samples to get ΔΔCt and fold change.

Instructions

Quantitative Real-Time PCR (qPCR) 2^(-ΔΔCt) Relative Gene Expression Calculator. Calculate relative gene expression fold change in RT-qPCR experiments using the Livak and Schmittgen comparative 2^(-ΔΔCt) quantification method. Discipline: BIOTECH. Governing mathematical model / formula: ΔΔCt = (Ct_target - Ct_ref)_treated - (Ct_target - Ct_ref)_control | Fold Change = 2^(-ΔΔCt).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of relative_fold_change_2_ddct (Relative Gene Expression Fold Change), delta_delta_ct_value (Comparative ΔΔCt Value), delta_ct_treated_sample (ΔCt (Treated Sample)), delta_ct_control_sample (ΔCt (Control Calibrator)) using target_gene_ct_treated (Target Gene Ct (Treated Sample) in Ct), reference_gene_ct_treated (Housekeeping Reference Ct (Treated) in Ct), target_gene_ct_control (Target Gene Ct (Untreated Control) in Ct), reference_gene_ct_control (Housekeeping Reference Ct (Control) in Ct). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Quantitative Real-Time PCR (qPCR) 2^(-ΔΔCt) Relative Gene Expression Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "qpcr-delta-delta-ct"

    • category (string): "biotech"

    • name (string): "Quantitative Real-Time PCR (qPCR) 2^(-ΔΔCt) Relative Gene Expression Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.relative_fold_change_2_ddct (Relative Gene Expression Fold Change): Formatted display string (e.g. '9.85-Fold Upregulation')

      • metrics.delta_delta_ct_value (Comparative ΔΔCt Value): Formatted display string (e.g. '-3.30 ΔΔCt')

      • metrics.delta_ct_treated_sample (ΔCt (Treated Sample)): Formatted display string (e.g. '+3.20 Ct')

      • metrics.delta_ct_control_sample (ΔCt (Control Calibrator)): Formatted display string (e.g. '+6.50 Ct')

    • execution_time_ms (number): Latency in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
target_gene_ct_controlNoTarget Gene Ct (Untreated Control) (Ct). Threshold cycle of gene of interest in vehicle control. Default: 24.8. Min: 5. Max: 40.
target_gene_ct_treatedNoTarget Gene Ct (Treated Sample) (Ct). Threshold cycle of gene of interest in experimental condition. Default: 21.4. Min: 5. Max: 40.
reference_gene_ct_controlNoHousekeeping Reference Ct (Control) (Ct). Threshold cycle of internal control in untreated control. Default: 18.3. Min: 5. Max: 40.
reference_gene_ct_treatedNoHousekeeping Reference Ct (Treated) (Ct). Threshold cycle of internal control (e.g. GAPDH, ACTB) in treated sample. Default: 18.2. Min: 5. Max: 40.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares pure deterministic computation, read-only/idempotent/stateless behavior with zero side effects, bounded input validation, and safe diagnostic errors rather than exceptions. The only shortfall is that the error semantics beyond 'status: error' are not detailed.

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?

Header-segmented and front-loaded with the purpose and formula, so scanning is easy. There is some bloat from repeating display names and units verbatim in the parameter lists and a long enumerated RETURNS block, but nothing that misleads.

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

Completeness5/5

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

For a four-parameter deterministic calculator, everything needed is present: formula, input roles with defaults and bounds, full return structure including each metric and example formats, and validation/error behavior. No output schema exists, yet the RETURNS section documents the response shape explicitly.

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% and each of the four Ct parameters already has a description with default and min/max bounds, so the schema carries parameter meaning. The description adds the role of each parameter in the ΔΔCt equation (target vs reference, treated vs control), but mostly by restating the schema labels with units.

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

Purpose5/5

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

Names a specific verb and resource ('Calculate relative gene expression fold change in RT-qPCR experiments') and pins the exact method (Livak and Schmittgen 2^(-ΔΔCt)). It also states the governing formula, so the agent can tell this apart from generic calculators without opening the schema.

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

Usage Guidelines5/5

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

Provides an explicit WHEN TO USE list mapped to the computed outputs and inputs, an explicit WHEN NOT TO USE (qualitative/unquantified reasoning, non-numeric inputs), and named alternatives: use omni_batch_calculate for chained jobs and omni_describe_solver for schema inspection instead of the generic omni_universal_query.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools