Skip to main content
Glama

Point-source workplane illuminance

bpj_eng_point_source_light
Read-onlyIdempotent

Estimate direct illuminance from luminous intensity, distance, and angle to the receiving surface normal.

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": {
      "intensity": "<intensity>",
      "distance": "<distance>",
      "angle": "<angle>"
    },
    "name": "bpj_eng_point_source_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYes
distanceYes
intensityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered and the bar is lower. The description adds the meaningful qualifier "direct" (no interreflection) and the geometry (angle to receiving surface normal), but says nothing about the underlying inverse-square/cosine model, output units, or validity limits of the point-source approximation.

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 no filler or repetition. It is efficient, though the terseness contributes to the specification gaps noted elsewhere.

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?

With no output schema, the description should say what comes back (lux, presumably) and state the governing relation; it does neither. For a simple three-number read-only calculator this is a moderate gap rather than a blocker, since the annotations and schema cover the mechanics of calling it.

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%, and the schema titles already supply names and units (deg, m, cd) with ranges. The description merely restates the three parameter names without adding semantics such as angle 0 meaning perpendicular incidence or how the parameters combine. It does not compensate for the coverage gap.

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?

Names a specific verb and resource ("Estimate direct illuminance") and names the three physical inputs that drive it. It does not, however, distinguish this from a nearby sibling such as bpj_units_illuminance, which an agent might plausibly confuse with a photometric illuminance calculation.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusions. The word "direct" hints that indirect/interreflected light is out of scope, but that is left to inference rather than 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.