Skip to main content
Glama

getecoback-climate-weather

led_spot_halbwertskreis_geometrie_arbeitsflaeche

Read-only

Für einen symmetrischen Spot den geometrischen Halbwerts-Durchmesser auf einer senkrechten Fläche veranschaulichen — Estimate the idealized beam footprint rather than inferring desk lux.

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": {
      "winkel_grad": "<winkel_grad>",
      "lotabstand_m": "<lotabstand_m>",
      "zielbreite_m": "<zielbreite_m>",
      "symmetrisch_und_senkrecht": "<symmetrisch_und_senkrecht>"
    },
    "name": "led_spot_halbwertskreis_geometrie_arbeitsflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
winkel_gradYesDokumentierter voller Halbwertswinkel; kein Messkegel des Nutzlichtstroms.
lotabstand_mYesAbstand zur idealisiert senkrecht zur optischen Achse liegenden Fläche in Metern.
zielbreite_mYesEigenes geometrisches Ziel auf derselben gedachten Fläche.
symmetrisch_und_senkrechtYesDieser Vergleich nimmt ein rundes Strahlbild und dieselbe senkrechte Achse an?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the important caveat that results are idealized geometry, not measured photometry. It does not say what the tool returns (presumably a diameter value) despite there being no output schema, leaving the response shape unstated.

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 the object of the computation first, followed by the usage contrast. The bilingual gloss is slightly redundant but short and does not bloat the definition.

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

Completeness4/5

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

Four required, fully documented parameters plus read-only annotations make the invocation side complete; the idealized-geometry caveat is the key thing an agent needs. The only gap is the unstated return value, which matters somewhat given there is no output schema.

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 100% and each parameter carries a precise German definition, so the schema does the heavy lifting. The description adds only the idealized-geometry framing and no per-parameter meaning beyond that, which is the baseline case.

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 computation: the geometric half-value diameter of a symmetric spot on a perpendicular surface ('geometrischen Halbwerts-Durchmesser auf einer senkrechten Fläche'). It also contrasts with a nearby concern ('rather than inferring desk lux'), which helps separate it from the beam-angle/lux siblings, though the distinguishing wording is thin.

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

Usage Guidelines3/5

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

The clause 'Estimate the idealized beam footprint rather than inferring desk lux' implies when this tool is appropriate instead of lux-based estimation. However, it does not name an alternative tool or state preconditions/exclusions for the symmetric-perpendicular case beyond passing the boolean flag.

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