Skip to main content
Glama

Macro subject field

bpj_design_macro_image_scale
Read-onlyIdempotent

Calculate object-space frame dimensions at the given optical reproduction ratio.

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>",
      "magnification": "<magnification>"
    },
    "name": "bpj_design_macro_image_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
sensorHYes
sensorWYes
magnificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the meaningful concept that results are in object space (subject plane) rather than image space, but says nothing about output units, whether both width and height are returned, or rounding conventions.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler. It is efficient but arguably over-compressed for a calculation tool where a clause on outputs and units would earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists and the description does not say what is returned (width and height in mm at the object plane) or in what shape. For a three-parameter calculation tool with 0% parameter documentation, the definition leaves too much for the agent to assume.

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%, so the description must carry parameter meaning, yet it only implicitly links 'optical reproduction ratio' to the magnification parameter and 'frame dimensions' to sensorW/sensorH. It never states units (mm), that sensor dimensions are the image-plane inputs, or how magnification is defined (image/object ratio).

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?

Specific verb ('Calculate') plus a specific resource ('object-space frame dimensions') conditioned on the optical reproduction ratio. The image-space vs object-space distinction helps separate it from siblings like bpj_design_lens_depth_range or bpj_design_camera_angle_of_view, though it never names an alternative.

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?

No when-to-use or when-not-to-use guidance, and no prerequisites or alternatives among the many design-math siblings. The agent can infer usage from the verb, but nothing steers selection when several tools take sensor/optical inputs.

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.