Skip to main content
Glama

Quantum Expectations

Historic Hardware Series (Fidelity or Qubit Count)

get_historic_series
Read-onlyIdempotent

Return the full historic time series — either two-qubit gate error rates ("fidelity") or physical qubit counts ("qubit-count") — broken down by hardware type. Each datapoint carries a source URL. It is the raw data behind trend questions such as "when might hardware reach X?"; fit_historic_series fits a log-linear trend to one hardware type's series.

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>"
    },
    "name": "get_historic_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesTypeYes"fidelity" → 2-qubit gate error rates; "qubit-count" → physical qubit counts.

Output Schema

NameRequiredDescriptionDefault
itemsYesOne series per hardware type.

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": {
      +    "items": {
      +      "description": "One series per hardware type.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "data": {
      +            "items": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "infidelity": {
      +                  "description": "Fidelity series only: 2-qubit gate infidelity.",
      +                  "type": "number"
      +                },
      +                "label": {
      +                  "type": "string"
      +                },
      +                "qubitCount": {
      +                  "description": "Qubit-count series only.",
      +                  "type": "number"
      +                },
      +                "source": {
      +                  "format": "uri",
      +                  "type": "string"
      +                },
      +                "year": {
      +                  "type": "number"
      +                }
      +              },
      +              "required": [
      +                "year",
      +                "source"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "name": {
      +            "description": "Hardware type.",
      +            "type": "string"
      +          },
      +          "note": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "data"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items"
      +  ],
      +  "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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds useful behavioral context beyond that: each datapoint carries a source URL, and the result is the 'full' series broken down by hardware type. It omits size/pagination expectations, which keeps it from a 5.

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 tight sentences with zero filler. The return value is front-loaded, provenance follows, and the sibling comparison closes the definition.

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?

With an output schema present, the description needn't detail return values, and it still conveys granularity (per hardware type), provenance (source URL), and the alternative tool. Nothing an agent needs to select or call this correctly is missing.

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 single enum parameter is already documented in the schema, so the baseline is 3. The description restates the fidelity/qubit-count mapping, reinforcing meaning but adding little beyond what the structured field provides.

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 and resource ('Return the full historic time series') and immediately enumerates the two modes ('fidelity' gate error rates vs 'qubit-count' physical qubits), plus the breakdown dimension ('by hardware type'). An agent can distinguish it from fit_historic_series without opening 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 concrete use case via an example question ('when might hardware reach X?') and explicitly contrasts with fit_historic_series, which 'fits a log-linear trend.' The routing logic (raw data here, fitting there) is clear, though it never states an explicit exclusion like 'do not use for trend fitting'.

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