Skip to main content
Glama

Neutral-density filter exposure

bpj_design_neutral_density_exposure
Read-onlyIdempotent

Calculate compensated exposure time and transmittance for a neutral-density filter rated in stops.

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": {
      "seconds": "<seconds>",
      "stops": "<stops>"
    },
    "name": "bpj_design_neutral_density_exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopsYes
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?

The annotations already declare this as a read-only, idempotent, closed-world, non-destructive calculation, so the safety profile is covered. The description adds that the result is a pair of derived values, compensated time and transmittance, which is useful context. It omits units, rounding, and formula details (for example whether transmittance is linear or per-stop).

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?

This is a single front-loaded sentence whose result clause and scoping clause both carry information. There is no filler or redundant restatement of the title.

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?

This is a simple two-parameter calculator with read-only annotations and no output schema, so the burden is light. The description names the two returned quantities but leaves their units and format unstated. That is adequate, though it could go one step further for an agent that has to consume the result.

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 has to carry parameter meaning, and it partly does: 'seconds' is identified as unfiltered exposure and 'stops' as the filter rating. The schema titles also help with 'Unfiltered exposure (s)' and 'Filter stops'. Neither the description nor the schema confirms the expected units of the returned compensated time or whether the input filter is absorptive density or optical density.

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 uses a specific verb and names both outputs: 'Calculate compensated exposure time and transmittance' and scopes it to 'a neutral-density filter rated in stops'. That is clearly more than a restatement of the name. It does not distinguish itself from nearby siblings such as bpj_design_photo_exposure_value, 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?

The definition says what it computes but never when an agent should choose it, nor when not to. With exposure-related siblings like bpj_design_photo_exposure_value present, a line ruling out the alternative would be valuable. Usage is only inferable from the photographic context of 'stops'.

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.