Skip to main content
Glama

Quantum Expectations

Measured QUOPS Capability Scores

list_quops_scores
Read-onlyIdempotent

Return the measured QUOPS (quantum universal operation performance system, a cross-platform capability benchmark) scores (arXiv:2609.12146): per device, the largest random universal circuit size executed at polarization >= 1/sqrt(e) inside the cone w^2 <= s <= w^3, with width, QUOPS rate, architecture (physical, physical-postselected, logical) and source URL, plus the utility-scale targets in the same unit (RSA-2048 and FeMoco). These are measurements, the yardstick the site's own model is checked against (modelCapability.quopsEquivalent in the compute_expectation hardware context). Vendor and device names appear here because this table is agent-facing only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
scoresYes
targetsYes
definitionYes
admissibleConeYes
polarizationThresholdYes

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": {
      +    "admissibleCone": {},
      +    "definition": {
      +      "type": "string"
      +    },
      +    "polarizationThreshold": {
      +      "type": "number"
      +    },
      +    "scores": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "architecture": {
      +            "enum": [
      +              "physical",
      +              "physical-postselected",
      +              "logical"
      +            ],
      +            "type": "string"
      +          },
      +          "code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "device": {
      +            "type": "string"
      +          },
      +          "discardFraction": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "hardwareType": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "physicalQubits": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "quopsRatePerSecond": {
      +            "type": "number"
      +          },
      +          "quopsScore": {
      +            "type": "number"
      +          },
      +          "source": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "vendor": {
      +            "type": "string"
      +          },
      +          "width": {
      +            "type": "number"
      +          },
      +          "year": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "device",
      +          "vendor",
      +          "hardwareType",
      +          "physicalQubits",
      +          "architecture",
      +          "code",
      +          "quopsScore",
      +          "width",
      +          "quopsRatePerSecond",
      +          "discardFraction",
      +          "year",
      +          "source"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "targets": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "id": {
      +            "type": "string"
      +          },
      +          "logicalQubits": {
      +            "type": "number"
      +          },
      +          "note": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "problem": {
      +            "type": "string"
      +          },
      +          "quopsRateTargetPerSecond": {
      +            "type": "number"
      +          },
      +          "quopsTarget": {
      +            "type": "number"
      +          },
      +          "resourceEstimateSource": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "source": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "timeBudget": {
      +            "type": "string"
      +          },
      +          "toffoliCount": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "problem",
      +          "logicalQubits",
      +          "toffoliCount",
      +          "quopsTarget",
      +          "quopsRateTargetPerSecond",
      +          "timeBudget",
      +          "resourceEstimateSource",
      +          "source",
      +          "note"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "definition",
      +    "polarizationThreshold",
      +    "admissibleCone",
      +    "scores",
      +    "targets"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds real context beyond them: data provenance (arXiv reference), that these are static measurements rather than computed results, and the unusual note that vendor/device names appear because the table is agent-facing only. It does not discuss freshness, units consistency, or completeness of device coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verb and resource are front-loaded, which is good, but the single densely packed sentence carries heavy apparatus — an acronym expansion, an arXiv identifier, and a polarization/cone formula — that an agent calling a no-parameter list tool rarely needs and that slows parsing. It is information-rich but not well-segmented.

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?

For a zero-parameter, read-only listing tool with an output schema, the definition supplies ample context: what the benchmark is, what each field means, its provenance, and its relation to the modeling tool. The only shortfall is that it never explicitly states the selection rule versus compute_expectation, leaving part of the routing to inference.

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?

With zero parameters there is nothing for the description to disambiguate, and the schema is empty, so the baseline of 4 applies. The description instead spends its words on what the returned rows mean, which is the relevant semantic content here.

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 opens with a specific verb and resource ('Return the measured QUOPS ... scores'), expands the acronym, and enumerates exactly what each row contains (largest random universal circuit size at a stated polarization threshold, width, rate, architecture, source URL, plus RSA-2048/FeMoco targets). It also contrasts itself with the modeled alternative (compute_expectation's modelCapability.quopsEquivalent), so an agent can tell measurement from model.

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

Usage Guidelines3/5

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

Usage is only implied: the text signals these are 'measurements, the yardstick the site's own model is checked against,' which hints at choosing this over compute_expectation when empirical values are needed. There is no explicit when-to-use or when-not statement, and no mention of the measurement-only scope as a selection criterion.

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