Skip to main content
Glama

Labreador — Bioassay & Ecotoxicology Calculators

Fit ELISA standard curve (4PL/5PL)

fit_standard_curve
Read-onlyIdempotent

Fit a 4PL or 5PL logistic curve to ELISA standards and optionally interpolate sample concentrations from their signals (OD). The result echoes the inputs received, lists data-quality warnings and includes the required Labreador citation.

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": {
      "concentrations": "<concentrations>",
      "signals": "<signals>"
    },
    "name": "fit_standard_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoStandard-curve model: 4PL (default) or asymmetric 5PL. Fewer than six standards with 5PL triggers an overfitting warning.4PL
signalsYes4 to 96 measured standard signals (for example OD), with exactly the same length and order as concentrations. Apply consistent blank correction before calling; negative signals trigger a warning.
sampleSignalsNoOptional array of up to 384 sample signals to interpolate using the fitted curve. Use the same signal units and blank correction as standards; returned concentrations follow this order and flag out-of-range values.
concentrationsYes4 to 96 positive ELISA standard concentrations, all in one unit. Exclude zero-concentration blanks; pair each entry with signals at the same position. Interpolated concentrations use this unit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / concentrations / description
      Previous value: -"Nonzero standard concentrations."New value: +"4 to 96 positive ELISA standard concentrations, all in one unit. Exclude zero-concentration blanks; pair each entry with signals at the same position. Interpolated concentrations use this unit."
    • addedInput schema / properties / concentrations / items / description
      Added value: +"One positive standard concentration in the common concentration unit."
    • changedInput schema / properties / model / description
      Previous value: -"Logistic model to fit."New value: +"Standard-curve model: 4PL (default) or asymmetric 5PL. Fewer than six standards with 5PL triggers an overfitting warning."
    • changedInput schema / properties / sampleSignals / description
      Previous value: -"Sample signals to convert to concentrations."New value: +"Optional array of up to 384 sample signals to interpolate using the fitted curve. Use the same signal units and blank correction as standards; returned concentrations follow this order and flag out-of-range values."
    • addedInput schema / properties / sampleSignals / items / description
      Added value: +"One sample signal in the same signal unit and blank-correction basis as the standards."
    • changedInput schema / properties / signals / description
      Previous value: -"Measured signal (OD) for each standard, same order."New value: +"4 to 96 measured standard signals (for example OD), with exactly the same length and order as concentrations. Apply consistent blank correction before calling; negative signals trigger a warning."
    • addedInput schema / properties / signals / items / description
      Added value: +"Measured signal for the corresponding standard, such as optical density (OD)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world computation. Beyond that, the description adds genuinely new behavioral detail: the result echoes the inputs, surfaces data-quality warnings, and carries a mandatory Labreador citation. It stops short of saying how warnings are formatted or what happens on a failed fit, but that is a minor gap for a pure calculation tool.

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?

Two sentences, zero waste, and the core action is front-loaded ahead of the optional interpolation and return-value details. Nothing is repeated from the schema or title.

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?

There is no output schema, so the description correctly spends its space explaining what comes back: echoed inputs, quality warnings, and the required citation. Combined with a fully documented four-parameter schema and read-only annotations, an agent has everything needed to call this correctly.

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%, and the schema itself explains model choice, signal/concentration ordering, blank-correction consistency, and the negative-signal and 5PL overfitting warnings. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

The description names a specific computational verb and resource: fitting a 4PL or 5PL logistic curve to ELISA standards, with optional interpolation of sample concentrations. An agent can immediately tell this apart from the unrelated siblings (dietary_risk, pollution_indices) 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 Guidelines4/5

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

It clearly establishes the context of use (ELISA standards, OD signals) and distinguishes the two modes of operation — curve fitting alone versus fitting plus sample interpolation via the optional sample signals. It does not state explicit exclusions or prerequisites (e.g., minimum standards), though the schema already carries the 4–96 constraint.

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