Skip to main content
Glama

Quantum Expectations

by com.quantum-expectations
OverviewDiscussionsAdmin

Compare Hardware Scenarios

compare_hardware_scenarios
Read-onlyIdempotent

Run the same circuit against multiple current SOTA hardware entries in one call so an agent can rank platforms without N sequential compute_expectation calls. Defaults to every entry in list_current_quantum_computers when hardwareIds is omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compDepthYes
numQubitsYes
hardwareIdsNoSubset of QUANTUM_COMPUTERS ids to compare. Omit to compare every entry.
useErrorCorrectionNo
distanceSurfaceCodeNoSurface code distance: odd integer in [3, 31]. Required when useErrorCorrection=true and the surface code is selected; ignored when a qLDPC code is selected.
errorCorrectionCodeNoEither "surface" (default when useErrorCorrection=true) or a qLDPC code id. "surface-code" is accepted as an alias for "surface".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / errorCorrectionCode / enum
      Previous value: -[
-  "surface",
-  "bb-144-12-12",
-  "surface-code"
-]New value: +[
+  "surface",
+  "bb-144-12-12",
+  "bb-288-12-18",
+  "surface-code"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / distanceSurfaceCode / description
      Previous value: -"Required when useErrorCorrection=true and errorCorrectionCode=\"surface\" (odd integer)."New value: +"Surface code distance: odd integer in [3, 31]. Required when useErrorCorrection=true and the surface code is selected; ignored when a qLDPC code is selected."
    • removedInput schema / properties / distanceSurfaceCode / maximum
      Removed value: -31
    • removedInput schema / properties / distanceSurfaceCode / minimum
      Removed value: -3
    • changedInput schema / properties / distanceSurfaceCode / type
      Previous value: -"integer"New value: +"number"
  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. Changed2 schema fields changed
    • changedInput schema / properties / errorCorrectionCode / description
      Previous value: -"Either \"surface\" (default when useErrorCorrection=true) or a qLDPC code id."New value: +"Either \"surface\" (default when useErrorCorrection=true) or a qLDPC code id. \"surface-code\" is accepted as an alias for \"surface\"."
    • changedInput schema / properties / errorCorrectionCode / enum
      Previous value: -[
-  "surface",
-  "bb-144-12-12"
-]New value: +[
+  "surface",
+  "bb-144-12-12",
+  "surface-code"
+]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: the single-call batching against multiple hardware entries and the default-to-all-hardware behavior when hardwareIds is omitted. It does not describe the return format, but that is more a completeness gap than a transparency one.

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 sentences with no filler. The primary purpose and the key usage condition are front-loaded, and the hardwareIds default is stated compactly in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives solid selection guidance and the default hardware behavior, but there is no output schema and the description never says what the returned comparison data looks like. For ranking platforms, an agent would benefit from knowing whether results include expectation values, error rates, or other metrics. Overall adequate for choosing the tool, but not fully complete for invoking it confidently.

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

Parameters2/5

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

The description adds almost no parameter-level meaning beyond the schema. The hardwareIds default is already documented in the schema, and the description does not clarify numQubits, compDepth, useErrorCorrection, or the error-correction code interactions. With schema description coverage at only 50%, the description should compensate but does not.

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 clearly states the tool runs the same circuit against multiple hardware entries in one call, which distinguishes it from sibling tools like compute_expectation and list_current_quantum_computers. The verb 'compare' plus the batching behavior make the purpose immediately clear.

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?

The description explicitly frames this as the tool to use when an agent wants to rank platforms without making N sequential compute_expectation calls. It also explains the default behavior when hardwareIds is omitted, giving an agent a clear selection and invocation rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Quantum Expectations toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources