Skip to main content
Glama

Quantum Expectations

Hardware Gate-Cycle Timings

list_hardware_timings
Read-onlyIdempotent

Return per-platform gate-cycle timings (two-qubit (2Q) gate time, readout time, in SI seconds) plus the testbed they were measured on (representativeDevice) and the native 2Q gate name, with source URLs. Joins list_current_quantum_computers via hardwareType, but the numbers are BEST-CASE DEMONSTRATIONS from small testbeds, not measurements on the joined devices, which run their gates and array readout orders of magnitude slower. As runtime inputs, including to compute_quantum_volume_rate, they give optimistic lower bounds.

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_hardware_timings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYesBest-case gate and readout times per platform.

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": "Best-case gate and readout times per platform.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "hardwareType": {
      +            "description": "Join key to list_current_quantum_computers.",
      +            "type": "string"
      +          },
      +          "native2QGate": {
      +            "type": "string"
      +          },
      +          "notes": {
      +            "type": "string"
      +          },
      +          "representativeDevice": {
      +            "description": "The testbed measured, not the joined current-hardware device.",
      +            "type": "string"
      +          },
      +          "t2QGateTime": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "seconds": {
      +                "description": "SI seconds.",
      +                "type": "number"
      +              },
      +              "source": {
      +                "format": "uri",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "seconds",
      +              "source"
      +            ],
      +            "type": "object"
      +          },
      +          "tMeasurement": {
      +            "additionalProperties": {},
      +            "properties": {
      +              "seconds": {
      +                "description": "SI seconds.",
      +                "type": "number"
      +              },
      +              "source": {
      +                "format": "uri",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "seconds",
      +              "source"
      +            ],
      +            "type": "object"
      +          }
      +        },
      +        "required": [
      +          "hardwareType",
      +          "representativeDevice",
      +          "native2QGate",
      +          "t2QGateTime",
      +          "tMeasurement"
      +        ],
      +        "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.8/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/closed-world profile, but the description adds the crucial semantic caveat that these values are optimistic lower bounds tied to representative testbeds rather than the joined production devices. This is precisely the kind of interpretation guidance an agent cannot derive from annotations or schema.

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 dense sentences, front-loaded with what is returned before the caveats, and every clause carries information (join key, testbed provenance, source URLs, unit of measure). The heavy parenthetical nesting makes it slightly harder to scan than an ideal 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 enumerate return fields in detail, and it still supplies the provenance, join relationship, and interpretation caveat that the schema cannot express. Nothing an agent needs to call and correctly interpret this tool is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description does clarify the units (SI seconds) of the returned quantities, which slightly helps but sits closer to output semantics than parameter semantics.

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?

Specific verb and resource: 'Return per-platform gate-cycle timings' with named fields (2Q gate time, readout time, SI seconds, representativeDevice, native 2Q gate name, source URLs). It also names the sibling it joins against (list_current_quantum_computers) via hardwareType, so an agent can distinguish it from the compute_* siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use: as runtime inputs, including for compute_quantum_volume_rate. Equally explicit when-not-to-trust: the numbers are best-case demonstrations from small testbeds, not the joined devices' actual performance, which is orders of magnitude slower. That is a rare and useful qualification of the consumption context.

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