Skip to main content
Glama

Quantum Expectations

Fit Historic Series (log-linear)

fit_historic_series
Read-onlyIdempotent

Fit a log-linear trend (ln(value) = slope * year + intercept) to one historic series — fidelity or qubit-count — for one hardware type. An atomic primitive for "when might hardware reach X?" questions; with targetValue it returns the year the fit reaches that value. residualStdDev is the BIASED (maximum-likelihood) root-mean-square (RMS) — divides by n, not (n - 2); on small series (n ≈ 3–5) the unbiased value is larger by √(n / (n - 2)).

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": {
      "seriesType": "<seriesType>",
      "hardwareType": "<hardwareType>"
    },
    "name": "fit_historic_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesTypeYesWhich historic series to fit: "fidelity" (2-qubit gate error rate) or "qubit-count" (physical qubits).
targetValueNoOptional. When supplied, the response includes yearAtTargetValue — the extrapolated year the fit crosses this value (error rate for fidelity series, qubit count for qubit-count series). Null if slope is flat.
hardwareTypeYesHardware platform as used by get_historic_series.

Output Schema

NameRequiredDescriptionDefault
modelYes
slopeYes
formulaYes
nPointsYes
interceptYes
yearRangeYes
seriesTypeYes
hardwareTypeYes
residualStdDevYesBiased (divide-by-n) RMS of the ln residuals.
yearAtTargetValueNoPresent only when targetValue was supplied.
halvingPeriodYearsYesNon-null iff slope < 0.
doublingPeriodYearsYesNon-null iff slope > 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "doublingPeriodYears": {
      +      "description": "Non-null iff slope > 0.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "formula": {
      +      "const": "ln(value) = slope * year + intercept",
      +      "type": "string"
      +    },
      +    "halvingPeriodYears": {
      +      "description": "Non-null iff slope < 0.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "hardwareType": {
      +      "type": "string"
      +    },
      +    "intercept": {
      +      "type": "number"
      +    },
      +    "model": {
      +      "const": "log-linear",
      +      "type": "string"
      +    },
      +    "nPoints": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "residualStdDev": {
      +      "description": "Biased (divide-by-n) RMS of the ln residuals.",
      +      "type": "number"
      +    },
      +    "seriesType": {
      +      "enum": [
      +        "fidelity",
      +        "qubit-count"
      +      ],
      +      "type": "string"
      +    },
      +    "slope": {
      +      "type": "number"
      +    },
      +    "yearAtTargetValue": {
      +      "description": "Present only when targetValue was supplied.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "yearRange": {
      +      "items": false,
      +      "maxItems": 2,
      +      "minItems": 2,
      +      "prefixItems": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "number"
      +        }
      +      ],
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "seriesType",
      +    "hardwareType",
      +    "model",
      +    "formula",
      +    "slope",
      +    "intercept",
      +    "nPoints",
      +    "residualStdDev",
      +    "yearRange",
      +    "halvingPeriodYears",
      +    "doublingPeriodYears"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the bar is lower. The description still adds real substance by disclosing that residualStdDev is the biased ML estimator dividing by n, with the exact √(n/(n-2)) correction for small samples, plus the flat-slope null case — statistical behavior an agent would otherwise misreport.

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?

Two sentences, front-loaded with purpose and formula, with the targetValue and estimator-bias caveats following in priority order. The second sentence is dense with parenthetical math, but every clause is substantive rather than filler.

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

Completeness4/5

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

With 100% schema coverage, full annotations, and an output schema, the description needs only purpose, use case, and caveats — all present. The one remaining gap is precondition handling: it references small series (n ≈ 3–5) but does not say what happens with insufficient or missing data points.

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 parameter already carries an enum or a precise description, so the baseline is 3. The description restates series scope and the targetValue return behavior but adds no format, units, or input-precondition detail beyond what the schema and output schema supply.

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?

States a specific verb (fit), resource (one historic series), the exact model (ln(value) = slope * year + intercept), and the scope (one series type, one hardware type). The formula plus the 'atomic primitive' framing separates it from multi-scenario siblings like compare_hardware_scenarios without needing to open either 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?

Gives a clear use context — "when might hardware reach X?" extrapolation questions — and notes that targetValue activates the year-at-target behavior. It names no explicit alternatives or when-not conditions (e.g., that raw series data comes from get_historic_series), so routing is clear but not fully disambiguated.

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