Skip to main content
Glama

Quantum Expectations

Example Quantum Algorithms

list_example_algorithms
Read-onlyIdempotent

Return the curated list of example quantum algorithms with published resource estimates (qubit count, depth/gate count, source paper URL). Useful for comparing what algorithms need vs. what hardware can deliver. Each entry carries a provenance field: 'published-circuit' means the figure is reproducible from the source, 'attested-estimate' means the source withholds the circuit and the figure rests on the authors' attestation, with a provenanceNote giving the specifics, so an attested figure is not sourced as firmly as a published circuit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYesCurated algorithms with published resource estimates.

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": "Curated algorithms with published resource estimates.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "compDepth": {
      +            "type": "number"
      +          },
      +          "compDepthDisplay": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "numQubits": {
      +            "type": "number"
      +          },
      +          "provenance": {
      +            "enum": [
      +              "published-circuit",
      +              "attested-estimate"
      +            ],
      +            "type": "string"
      +          },
      +          "provenanceNote": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "source": {
      +            "format": "uri",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "numQubits",
      +          "compDepth",
      +          "compDepthDisplay",
      +          "source",
      +          "provenance",
      +          "provenanceNote"
      +        ],
      +        "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.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuinely non-schema context: the provenance taxonomy distinguishing 'published-circuit' from 'attested-estimate' and the warning that attested figures are less firmly sourced. That is real trustworthiness guidance an agent cannot derive from annotations.

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?

The purpose and the comparison use-case are front-loaded in the first sentence, with provenance detail after. The provenance sentence is long and packs two definitions plus a caveat into one breath, which is slightly dense but every clause carries information the agent needs.

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?

An output schema exists and the tool has no inputs, so the description only needs to convey purpose, trust semantics, and use case — which it does. The one nuance worth extra words, the provenance field's meaning, is explicitly spelled out rather than left to the schema.

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 there is nothing for the description to disambiguate and the baseline is 4. The field-level detail about provenance is about returned data rather than inputs, which is helpful but does not change the parameter score.

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 curated list of example quantum algorithms with published resource estimates," and immediately scopes the content to qubit count, depth/gate count, and source paper URL. That is enough for an agent to separate it from compute-oriented siblings like compute_fault_tolerant_resources or list_current_quantum_computers.

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 through "Useful for comparing what algorithms need vs. what hardware can deliver," which suggests a pairing with the hardware-listing tools but never states when to call this instead of them. No exclusions, prerequisites, or explicit alternative are given, so the agent must infer the routing.

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