ScienceShot science reference

Thermal and shot noise

noise_calculator

Read-onlyIdempotent

Calculate Johnson-Nyquist thermal noise voltage, current and available power kTB, Schottky shot noise, noise figure and noise temperature (290 K reference), input noise floor and SNR in dB, and the ideal ADC quantization SNR (6.02 N + 1.76 dB) with ENOB from a measured SINAD. Classical white-noise formulas with CODATA 2018 constants; every answer cites Johnson, Nyquist, Schottky, Friis and Kester.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resistance_ohm": "<resistance_ohm>",
      "temperature_k": "<temperature_k>",
      "bandwidth_hz": "<bandwidth_hz>"
    },
    "name": "noise_calculator"
  }
}

Input Schema

Name	Required	Description
`bits`	No	ADC resolution, integer 1 to 64; default 12.
`sinad_db`	No	Measured ADC SINAD in dB, at least 1.76; default 74.
`current_a`	No	DC current for shot noise in ampere, 0 or more; default 0.
`signal_dbm`	No	Signal power at the input in dBm; default -100.
`bandwidth_hz`	Yes	Noise bandwidth in hertz, greater than 0.
`temperature_k`	Yes	Temperature in kelvin, greater than 0.
`resistance_ohm`	Yes	Resistance in ohm, greater than 0.
`noise_figure_db`	No	Noise figure in dB, 0 to 200; default 0.
`noise_temperature_k`	No	Optional noise temperature in kelvin; overrides the noise figure.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the read-only, idempotent annotations, the description discloses that results are formula-based using CODATA 2018 constants and that every answer cites Johnson, Nyquist, Schottky, Friis, and Kester. It also states the 290 K reference for noise figure and noise temperature. It does not discuss error conditions or validity limits, but it adds meaningful behavioral context beyond structured 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 definition is a single dense sentence with no filler, and the main purpose is front-loaded. However, the long run-on enumeration of outputs makes it harder to scan than a structured list would be, so it stops short of ideal conciseness and structure.

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?

For a nine-parameter calculator with no output schema, the description covers all major calculation families and names the returned quantities, including voltage, current, power, SNR in dB, and ENOB. It does not describe the return structure or error behavior, but it is complete enough for an agent to understand what the tool computes and how to invoke it.

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 description coverage is 100%, with every parameter documented, so the schema already carries the parameter semantics. The description adds the 290 K reference for noise temperature and noise figure, but it does not map inputs such as resistance, temperature, bandwidth, current, bits, and SINAD to their specific roles. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb, "Calculate", and enumerates concrete noise quantities: Johnson-Nyquist thermal noise, Schottky shot noise, noise figure, noise temperature, SNR, and ADC quantization SNR/ENOB. This is far more specific than a restatement of the title, though it does not explicitly differentiate itself from any sibling tool.

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?

The phrase "Classical white-noise formulas" implicitly scopes usage to white-noise calculations and excludes other noise types, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives are named, which is acceptable given the sibling list contains no similar noise calculator, but the guidance remains implied rather than stated.

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

All ScienceShot science 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?