Skip to main content
Glama

Lens depth-of-field range

bpj_design_lens_depth_range
Read-onlyIdempotent

Estimate near and far acceptable focus points from focal length, f-number, focus distance, and circle of confusion.

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": {
      "focal": "<focal>",
      "fNumber": "<fNumber>",
      "focus": "<focus>",
      "coc": "<coc>"
    },
    "name": "bpj_design_lens_depth_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
cocYes
focalYes
focusYes
fNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description needs only to add computation-specific context. It does add one substantive fact beyond annotations — that the result is a pair of near/far focus limits — but says nothing about output units, the convention used, or validity limits (e.g. focus distance beyond hyperfocal), which matter for a formula tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the inputs listed in a natural order after the output statement, so the purpose is front-loaded and nothing is redundant. It is neither padded nor truncated for a four-parameter calculation tool.

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

Completeness3/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 is the only place return values can be characterized, and it only gestures at them ("near and far acceptable focus points") without units or form. For a pure numeric estimator with four required inputs this is minimally adequate but leaves the agent guessing about the return shape.

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%, so the description carries the burden, yet it only enumerates the four inputs by generic name ("focal length, f-number, focus distance, and circle of confusion") without stating units, accepted ranges, or the units of the result. The schema's own titles supply units (mm, m) that the description omits, and crucially the mixed mm-vs-metres convention is not clarified in prose.

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 pairs a specific verb ("Estimate") with a specific resource ("near and far acceptable focus points"), which is unambiguously a depth-of-field calculation and clearly distinct from optical siblings such as bpj_design_diffraction_disk or bpj_design_camera_angle_of_view. It stops short of naming any sibling or stating explicit boundaries, so it lands at clear-but-undifferentiated.

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 or constraints on the inputs, and no alternative tool is referenced. The usage context is only inferable from the photographic subject matter of the inputs.

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.