Skip to main content
Glama

Quantum Expectations

Current Quantum Computers

list_current_quantum_computers
Read-onlyIdempotent

Return the representative-entry table of current state-of-the-art quantum computers (id, hardware type, physical qubit count, 2-qubit error rate, connectivity class with a note on the coupling graph, source URL). Same data that powers the website's "Current Quantum Computers" table. The model's capability prediction per entry in QUOPS units is served by compute_expectation (hardwareContext.currentQuantumComputers[].modelCapability); measured scores are in list_quops_scores.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYesOne representative entry 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 representative entry per hardware type.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "connectivity": {
      +            "enum": [
      +              "all-to-all",
      +              "reconfigurable",
      +              "2d-lattice"
      +            ],
      +            "type": "string"
      +          },
      +          "connectivityNote": {
      +            "type": "string"
      +          },
      +          "errorRate": {
      +            "description": "2-qubit gate error rate as a probability.",
      +            "type": "number"
      +          },
      +          "errorRateDisplay": {
      +            "type": "string"
      +          },
      +          "hardwareType": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Stable alias accepted as hardwareId by the compute tools.",
      +            "type": "string"
      +          },
      +          "physicalQubits": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "source": {
      +            "format": "uri",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "physicalQubits",
      +          "errorRate",
      +          "errorRateDisplay",
      +          "hardwareType",
      +          "connectivity",
      +          "connectivityNote",
      +          "source"
      +        ],
      +        "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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful non-annotation context: this is a curated 'representative-entry' set rather than an exhaustive catalog, it mirrors the website table, and it carries a coupling-graph note in the connectivity field — all of which shape how an agent should treat the results. It stops short of describing size, ordering, or freshness of the table.

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?

Three sentences, front-loaded with the purpose and the returned fields, followed by sibling routing. It is dense but each clause carries information; the 'same data that powers the website's table' sentence is mild context padding but does convey provenance/curation.

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 an output schema present and full annotation coverage, the description need not explain return values — yet it still summarizes fields and points to where richer derived data lives. The one gap is that it doesn't indicate whether the representative list is static or occasionally refreshed, which matters for an agent reporting 'current' state.

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 zero parameters, so the baseline is 4; there are no parameter semantics to document. The description correctly implies no filtering is possible and adds no misleading input expectations.

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 representative-entry table of current state-of-the-art quantum computers') and enumerates the fields returned (id, hardware type, qubit count, error rate, connectivity class, source URL). It also explicitly separates itself from compute_expectation (modeled capability) and list_quops_scores (measured scores), so an agent can distinguish it from siblings without opening the 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?

It routes the agent to the right sibling for adjacent needs: capability predictions live in compute_expectation and measured results in list_quops_scores. What's missing is an explicit statement of when to call this tool (e.g., 'call this first to discover hardware ids'), but the context is clear enough to guide selection.

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