Skip to main content
Glama

Projector throw dimensions

bpj_design_projection_throw
Read-onlyIdempotent

Estimate projected picture width, height, and diagonal from throw ratio, distance, and aspect 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": {
      "distance": "<distance>",
      "throwRatio": "<throwRatio>",
      "ratioW": "<ratioW>",
      "ratioH": "<ratioH>"
    },
    "name": "bpj_design_projection_throw"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioHYes
ratioWYes
distanceYes
throwRatioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 needs no restating. The description's main addition is naming the three returned values, which matters because there is no output schema. It omits unit behavior for the results (inputs are metric) and any assumption such as an ideal lens with no zoom or keystone correction, which would materially affect the estimate.

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?

One front-loaded sentence with no filler and no repetition of the title. It could earn slightly more by folding in the output unit or the assumption in the same sentence without adding length.

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 pure four-number calculator with no output schema, the description should establish input-output mapping (it does) and unit/assumption context (it does not). Nothing about the return format beyond the names of the three values is given, leaving an agent to guess result units.

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%, but the schema's own titles carry useful semantics ('Throw distance (m)', 'Throw ratio (distance/width)', 'Aspect width', 'Aspect height'). The description adds only that the aspect ratio is a single conceptual input split into width/height parts, plus which fields produce which outputs; it does not clarify bounds, unit propagation to results, or how the ratio pairs are combined.

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 verb and output set: 'Estimate projected picture width, height, and diagonal,' and enumerates the three input concepts (throw ratio, distance, aspect ratio). This clearly separates it from sibling optics tools like bpj_design_camera_angle_of_view or bpj_design_lens_depth_range, though it never explicitly contrasts with them.

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 guidance, no prerequisites, and no mention of alternatives. The agent must infer the use case (planning projector placement) entirely from the parameter list. The implied usage is discernible but nothing is stated.

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.