Skip to main content
Glama

Diffraction spot diameter

bpj_design_diffraction_disk
Read-onlyIdempotent

Calculate the theoretical Airy disk diameter at the image plane for a circular aperture.

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": {
      "wave": "<wave>",
      "fNumber": "<fNumber>"
    },
    "name": "bpj_design_diffraction_disk"
  }
}

Input Schema

NameRequiredDescriptionDefault
waveYes
fNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds the meaningful caveat that the result is theoretical and measured at the image plane for a circular aperture, but omits output units and any note about the approximation's validity.

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. It is appropriately sized, though it is perhaps too lean for a numeric calculator whose output units are unspecified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should state what comes back and in what units (e.g., nm or µm diameter) — it does not. For a two-parameter numeric calculator with zero schema description coverage, the definition leaves the agent guessing on the result's interpretation.

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%, and the description contributes nothing about 'wave' or 'fNumber' — no unit conventions beyond the title, no note that wavelength is in nanometres and must fall in 300–1100, and no mention of what f-number physically means here. The field names are largely self-explanatory, which keeps this above 1.

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?

States a specific computation ('Airy disk diameter'), the domain ('theoretical', 'image plane'), and the configuration ('circular aperture'). This clearly distinguishes it from sibling design calculators such as depth-of-range or angle-of-view, though it does not name an alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to a related or alternative tool. The only implied usage context is the phrase 'theoretical ... at the image plane', which the agent must interpret on its own.

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.