ScienceShot data-centre intelligence and physics reference

Qubit coherence and gate fidelity calculator

qubit_coherence

Read-onlyIdempotent

Calculate single-qubit average fidelity under Markovian amplitude/phase damping using Nielsen (2002). Accept T1, T2 or Tphi and gate time; checks T2 <= 2T1 and returns pure dephasing, error per gate and an independent-error depth proxy, not a circuit-success guarantee.

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": "qubit_coherence"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Whether t2_us denotes T2 or Tphi; default t2.
`t1_us`	No	Relaxation T1 (microseconds); default 100.
`t2_us`	No	T2 or Tphi (microseconds); default 100.
`gate_ns`	No	Gate time (ns); default 20.
`success`	No	Target success proxy P (0 to 1); default 0.99.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish a safe, read-only, idempotent, closed-world computation. The description adds real value beyond them: the T2 <= 2T1 validity check, the outputs (pure dephasing, error per gate, depth proxy), and a caveat that the depth proxy is not a circuit-success guarantee.

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?

A single dense sentence that front-loads the computation, then the inputs, then the validity check and outputs. Efficient with no filler, though the run-on structure with parentheses and a list makes it slightly harder to scan than two short sentences would.

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 no output schema, the description correctly names the returned quantities and the validation rule an agent must anticipate. It omits default values and units (covered in the schema) and doesn't describe the failure behavior when T2 > 2T1, a minor gap for a deterministic calculator.

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

Parameters3/5

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

Schema coverage is 100%, so units, defaults and the mode enum are already documented. The description adds the relationship between t1_us/t2_us and the chosen mode, but says nothing about the 'success' target parameter, leaving that entirely to the schema. Baseline 3 applies.

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?

States a specific verb and resource: 'Calculate single-qubit average fidelity under Markovian amplitude/phase damping using Nielsen (2002).' The model, regime and citation make it unambiguous and clearly distinct from every sibling tool (beam, detector, dose, etc.).

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?

Explains the input contract (accept T1, T2 or Tphi plus gate time) and the constraint checked (T2 <= 2T1), and sets a boundary by noting the depth proxy is 'not a circuit-success guarantee.' No explicit when-not-to-use or alternative tool is named, but no sibling overlaps this domain.

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

All ScienceShot data-centre intelligence and physics reference tools Inspect

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

Need Help?