Skip to main content
Glama

Cinema shutter angle exposure

bpj_design_shutter_angle
Read-onlyIdempotent

Calculate each frame’s exposure duration and reciprocal shutter setting from shutter angle and frame rate.

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": {
      "angle": "<angle>",
      "fps": "<fps>"
    },
    "name": "bpj_design_shutter_angle"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsYes
angleYes

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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the substantive behavioral fact that the tool returns both a duration and a reciprocal shutter value, which is useful, but it says nothing about output units or edge-case handling (e.g., 360° returning 1/fps).

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; every clause maps to an input or an output. Nothing is redundant and nothing is buried.

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 two-parameter pure calculator with full annotations and no output schema, the core is covered. What is missing is any indication of result format (seconds vs. fraction) or behavior at the parameter boundaries (0.001°–360°, 0.001–1,000,000 fps), which would matter for an agent presenting results.

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 0%, so the description must carry parameter meaning, and it does name both inputs and their roles. However, the schema titles already specify 'Shutter angle (deg)' and 'Playback frame rate (fps)', including valid ranges, so the description contributes little beyond mapping the two names into the computation.

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 verb ('Calculate') and specific outputs ('exposure duration and reciprocal shutter setting') from two named inputs. An agent immediately knows what goes in and what comes out. It does not distinguish itself from adjacent exposure calculators such as bpj_design_photo_exposure_value or bpj_design_neutral_density_exposure, so it stops short of a 5.

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, when-not-to-use, or alternative-tool guidance; the description is purely a statement of computation. The agent can infer the domain (cinema shutter math) from the name and inputs, but nothing tells it when this tool is the right choice over the other exposure-related siblings.

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.