Skip to main content
Glama

Rectilinear camera field of view

bpj_design_camera_angle_of_view
Read-onlyIdempotent

Find horizontal, vertical, and diagonal angle of view of a rectilinear lens at infinity focus.

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": {
      "sensorW": "<sensorW>",
      "sensorH": "<sensorH>",
      "focal": "<focal>"
    },
    "name": "bpj_design_camera_angle_of_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
focalYes
sensorHYes
sensorWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is covered. The description does add real modeling context — that the result assumes a rectilinear projection at infinity focus, which matters for interpretation — but says nothing about the units of the returned angles or any handling of degenerate inputs.

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 front-loaded sentence with no filler. The defining constraints (rectilinear, infinity focus) appear immediately after the verb and resource, so nothing needs to be skimmed for.

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?

For a simple three-number calculation this is nearly adequate, but with no output schema the description should state what is returned — whether the three angles come back in degrees or radians and in what structure — and it omits that entirely. The rectilinear/infinity-focus assumption is the main thing it gets right.

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% for three required numeric parameters, so the description is the only place to compensate, and it does not. It never names sensorW, sensorH, or focal, and adds no units, expected ranges, or the constraint that all three must be positive and in millimeters beyond what the bare titles already state.

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?

"Find horizontal, vertical, and diagonal angle of view" gives a specific verb and a precisely named resource, and the qualifiers "rectilinear lens at infinity focus" narrow it well away from sibling optics tools such as bpj_design_lens_depth_range or bpj_design_shutter_angle. It stops short of naming an alternative, so it is clear but not maximally differentiated.

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?

There is no explicit when-to-use or when-not-to-use statement and no alternative is named. The phrase "at infinity focus" implicitly scopes out close-focus/macro cases, which is useful, but an agent must infer the rest of the applicability from the purpose sentence alone.

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.