Skip to main content
Glama

Photographic exposure value

bpj_design_photo_exposure_value
Read-onlyIdempotent

Find the camera setting EV and ISO-100 equivalent scene EV from aperture, exposure time, and ISO.

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": {
      "fNumber": "<fNumber>",
      "seconds": "<seconds>",
      "iso": "<iso>"
    },
    "name": "bpj_design_photo_exposure_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoYes
fNumberYes
secondsYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that two results are computed rather than one, which is genuinely useful, but says nothing about invalid input combinations, precision, or what the returned values represent numerically.

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?

One sentence, front-loaded with the verb and the two outputs, then the inputs. No filler and nothing repeated from the schema.

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 small pure-calculation tool with four annotations and no output schema, the definition is close to adequate, but with no output schema the description should clarify what 'ISO-100 equivalent scene EV' means as a return value and in what units. The absence of any note on invalid or out-of-range input handling leaves a gap.

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; it partially does by mapping 'aperture' to fNumber, 'exposure time' to seconds, and 'ISO' to iso. The schema's titles and min/max bounds already convey units and ranges, and the description adds no format or edge-case detail beyond the name mapping.

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 names a specific computation (exposure value), the inputs that drive it (aperture, exposure time, ISO), and the two quantities produced (camera setting EV and ISO-100 equivalent scene EV). That is far more informative than the bare title, though it never distinguishes this from related photographic calculators such as bpj_design_neutral_density_exposure.

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 statement of prerequisites, and no routing to alternatives. An agent must infer from the input names alone that this applies to photographic exposure calculations rather than the neighbouring design and exposure tools.

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.