ibm-quantum
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IBM_QUANTUM_API_KEY | No | Alternative raw credential supplied by the process environment; takes precedence over IBM_QUANTUM_API_KEY_FILE. | |
| IBM_QUANTUM_INSTANCE | No | Optional default instance CRN. | |
| IBM_QUANTUM_MAX_SHOTS | No | Per-call shot setting ceiling; default 8192, maximum 1000000. | 8192 |
| IBM_QUANTUM_API_KEY_FILE | No | Path to an IBM JSON export containing `apikey`. Recommended credential source. | |
| IBM_QUANTUM_MAX_EXECUTION_SECONDS | No | Per-job QPU execution ceiling; default 60, maximum 10800. | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quantum_configurationA | Show credential presence and configured limits without reading or returning the API key. |
| quantum_instancesA | Authenticate with IBM and list accessible instance CRNs, names, and plans; no compute is submitted. |
| quantum_backendsB | List accessible QPUs, availability, queue lengths, qubits, and supported gates for an instance. |
| quantum_simulateA | Simulate up to 20 qubits locally without IBM authentication or charges. Measure every qubit at end. |
| quantum_previewA | Transpile for a specific IBM backend and report depth/gate counts without submitting a job. |
| quantum_run_samplerA | Sample a circuit, measuring all qubits. Default dry_run previews only. False submits one quota-consuming job and returns its ID immediately. |
| quantum_run_estimatorA | Estimate one weighted Pauli-sum observable. Pauli rightmost character is qubit 0. Shots is per measurement configuration, not total shots. False submits hardware work; default previews only. |
| quantum_jobsA | List recent jobs for an instance. Page with skip. Use after ambiguous submission errors to avoid duplicates. |
| quantum_jobA | Read job status and results. Default does not wait for queued work. Results include up to 20 PUBs, register counts or expectation values; large results are explicitly marked truncated. |
| quantum_cancel_jobA | Request cancellation of the specified unfinished IBM job. Already consumed QPU time remains consumed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target distinct stages of the quantum workflow (config, discovery, preview, submit, monitor), but the pair quantum_job (read one job) and quantum_jobs (list jobs) differ only by a trailing 's', which is a real misselection hazard. quantum_preview also overlaps conceptually with the dry-run defaults of quantum_run_sampler/quantum_run_estimator, though descriptions distinguish them.
All names share a consistent quantum_ snake_case prefix, giving a predictable namespace. However, the set mixes noun-only names (quantum_configuration, quantum_backends, quantum_instances) with verb_noun names (quantum_cancel_job, quantum_run_sampler) and relies on singular/plural to distinguish get vs list.
Ten tools is well within the ideal range and each maps to a genuine step: credentials, instance/backend discovery, local simulation, transpile preview, sampler and estimator submission, job listing, job read, and cancellation. No tool feels redundant or vestigial.
The surface covers the full submit-preview-monitor-cancel lifecycle plus local simulation and discovery, which is strong coverage for a quantum backend client. Minor gaps remain: no session/batch management, no job deletion or log retrieval, and no tool to validate or build circuits before preview.