ScienceShot science reference

CCD vs CMOS SNR calculator

image_sensor_snr

Read-onlyIdempotent

Compare electron-domain CCD, CMOS and EMCCD signal-to-noise with binning, stacking, PRNU and saturation.

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": {
      "a": "<a>",
      "b": "<b>",
      "common": "<common>"
    },
    "name": "image_sensor_snr"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes
`common`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3/5.0

Behavior2/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. Beyond that the description only lists modelling domains; it does not say what the tool returns (per-architecture SNR only, or a delta/ratio), what units apply, how saturation clipping is reported, or what assumptions the electron-domain model makes.

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 front-loaded sentence with no filler, and the domain qualifier ('electron-domain') sits early where it matters. It is efficient, though the density of unexplained terms means the brevity is partly under-specification rather than economy.

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?

No output schema exists and the parameters carry almost no inline documentation, so the description would need to explain the return shape (comparison result, saturation handling) and the meaning of the nested device objects. Neither is present, leaving this inadequate for a tool with nested configuration objects and three required top-level arguments.

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?

Schema description coverage is 0% at the top level and the nested fields qe, prnu, full_well_e, em_gain, em_well, excess_f2, register_factor, P, t, n and m are almost entirely undocumented. The description's mention of 'binning' and 'stacking' loosely maps to n and m, but it never states that n is binning factor and m is frames stacked, nor that 'a' and 'b' are the two devices under comparison.

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?

Specific verb and resource: 'Compare electron-domain CCD, CMOS and EMCCD signal-to-noise', and it names the modelling features (binning, stacking, PRNU, saturation) that scope the calculation. It implicitly distinguishes itself from modelling siblings such as detector_signal or noise_calculator, though it does not name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus detector_signal, noise_calculator, or photodiode_responsivity, and no preconditions. The word 'Compare' hints that two device configs are expected, but the agent must infer that 'a' and 'b' are the two devices being compared rather than being told.

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?