Skip to main content
Glama

Quantum Expectations

Compute Quantum Volume Rate

compute_quantum_volume_rate
Read-onlyIdempotent

Compute the Quantum Volume Rate (QVR, in Quantum Volume (QV) per second): QVR = V_Q / (log2(V_Q) * t_2Q + t_meas). First-order estimate of how fast a device prepares one QV-sized square circuit (one native 2Q gate per QV layer + one end-of-circuit measurement). OVERSTATES achievable rate: real compilation inflates the 2Q-gate count per layer; omits reset, state preparation and measurement (SPAM), mid-circuit measurement, and classical-control latency. It is not a production throughput metric such as IBM's CLOPS (circuit layer operations per second, arXiv:2110.14108).

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": {
      "quantumVolume": "<quantumVolume>",
      "t2QSeconds": "<t2QSeconds>",
      "tMeasurementSeconds": "<tMeasurementSeconds>"
    },
    "name": "compute_quantum_volume_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
t2QSecondsYesNative 2-qubit gate time in seconds (e.g. 60e-9 for a 60 ns CZ).
quantumVolumeYesQuantum volume V_Q (integer ≥ 2, e.g. 64 for a depth-log2=6 square circuit).
tMeasurementSecondsYesEnd-of-circuit measurement/readout time in seconds (e.g. 5e-3 for 5 ms).

Output Schema

NameRequiredDescriptionDefault
unitYes
inputsYes
caveatsYes
formulaYes
assumptionsYes
qvrPerSecondYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / t2QSeconds / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / t2QSeconds / minimum
      Added value: +1e-18
    • removedInput schema / properties / tMeasurementSeconds / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / tMeasurementSeconds / minimum
      Added value: +1e-18
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "assumptions": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "caveats": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "formula": {
      +      "type": "string"
      +    },
      +    "inputs": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "quantumVolume": {
      +          "type": "number"
      +        },
      +        "t2QSeconds": {
      +          "type": "number"
      +        },
      +        "tMeasurementSeconds": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "quantumVolume",
      +        "t2QSeconds",
      +        "tMeasurementSeconds"
      +      ],
      +      "type": "object"
      +    },
      +    "qvrPerSecond": {
      +      "type": "number"
      +    },
      +    "unit": {
      +      "const": "QV/s",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "qvrPerSecond",
      +    "unit",
      +    "formula",
      +    "inputs",
      +    "assumptions",
      +    "caveats"
      +  ],
      +  "type": "object"
      +}
  3. 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"
  4. 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 read-only, idempotent, closed-world, non-destructive behavior, so the description is not needed for safety. It still adds real value by disclosing the model's systematic bias ('OVERSTATES achievable rate') and the specific omissions (compilation overhead, reset, SPAM, mid-circuit measurement, classical control). It stops short of stating domain validity limits or error behavior.

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?

Front-loads the definition and formula, then the caveats and the contrast with CLOPS. It is dense and the middle sentence is long, but every clause carries information; nothing is 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?

Given three fully described required parameters and an output schema, the description covers the definition, the computation, and the interpretation caveats an agent needs. The only gap is guidance on interpreting or sanity-checking an unexpectedly large or zero result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes further by embedding each parameter in the formula and explaining its role ('one native 2Q gate per QV layer', 'one end-of-circuit measurement'), which tells the agent how the inputs interact rather than just what each one is.

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 (compute the Quantum Volume Rate) and gives the exact formula QVR = V_Q / (log2(V_Q) * t_2Q + t_meas), plus a plain-language gloss of what that rate means physically. It also explicitly distinguishes itself from a nearby metric (IBM CLOPS), so an agent can tell what it is and is not.

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?

Makes the intended use clear ('first-order estimate') and explicitly warns against a misuse ('not a production throughput metric such as IBM's CLOPS'). What is missing is any routing to sibling tools or a statement of when another tool (e.g. compute_required_error_rate or compare_hardware_scenarios) would be preferred.

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