Skip to main content
Glama

WritersLogic business agents

exposure-calc

Photographic exposure value: solve aperture, shutter, ISO or EV, with equivalent exposures — Given any three of aperture (f-number), shutter time in seconds, ISO and scene EV at ISO 100, solves the fourth from EV = log2(N^2/t) and EV_S = EV_100 + log2(S/100), names the nearest one-third-stop f-number, and lists the equivalent shutter time at each f-number from f/1 to f/32. Given all four, checks that they agree within a tolerance in stops. Built for camera, lighting and image-generation a

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exposure-calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoNoISO speed S.
ev100NoScene light as exposure value at ISO 100.
apertureNof-number N.
shutterSecondsNoExposure time t in seconds.
toleranceStopsNoWhen all four are given: largest EV100 disagreement accepted (default 0.05).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of it: it discloses the formulas used, that the result includes the nearest one-third-stop f-number, and that a table of equivalent shutter times from f/1 to f/32 is returned, making clear this is a deterministic read-only calculation. It omits error behavior when fewer than three parameters are supplied, and the text is visibly truncated mid-sentence ('...image-generation a'), leaving the intended-use context incomplete.

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

Conciseness3/5

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

The lead clause is well front-loaded and every clause carries information, but the body is a single dense run-on packing two formulas and two output behaviors into one sentence. The trailing fragment 'Built for camera, lighting and image-generation a' is a truncated sentence that adds noise rather than value.

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?

There is no output schema, so the description must describe returns, and it does so only partially: it mentions the nearest one-third-stop f-number and the equivalent shutter list but not the overall response shape or units of the tolerance check result. Combined with the truncated closing sentence and unstated behavior for insufficient inputs, the definition is adequate but leaves real gaps for a five-parameter solver.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds meaning beyond the schema by explaining how the parameters relate through EV = log2(N^2/t) and EV_S = EV_100 + log2(S/100). It also clarifies that any three are sufficient and that toleranceStops applies only when all four are present, which the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-plus-resource phrase ('Photographic exposure value: solve aperture, shutter, ISO or EV') and then names the exact governing equations, so an agent knows precisely what computation the tool performs. It is unambiguously distinct from calculator siblings such as electrical-calc by domain and by the aperture/shutter/ISO parameter set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly delineates two operating modes: 'Given any three of aperture... solves the fourth' and 'Given all four, checks that they agree within a tolerance in stops,' which is real when-to-use guidance for the two invocation styles. It stops short of explicit exclusions or guidance on what happens with fewer than three inputs, so it falls short of a 5.

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.

Resources