Skip to main content
Glama

led_select

Read-only

Calculation-based LED selection by package, CCT, and operating current. If there is no current, call led_catalog_search (price list without calculation) or ask for the current. Default: 5 items, maximum 10 — if the user asks for more, call with limit 10. Without availability — stock and on order only; availability.source=all — all items. Without sort — lowest cost per lumen; with thresholds.target_flux the sort is always flux-distance-asc, and flux-distance-asc without it is rejected as sort-invalid. Show the result as the table from the response table field — it is the same as on the site. Pass hidden_message to the user; do not promise an order.

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": {
      "catalog": "<catalog>",
      "current": "<current>"
    },
    "name": "led_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoresult sorting: price-per-lumen-usd-asc — lowest cost per lumen (USD/lm), price-usd-asc — lowest price per unit (USD), price-cny-asc — lowest price per unit (CNY), efficacy-desc — highest efficacy, flux-desc — highest flux, flux-distance-asc — closest to the specified target flux, only with target_flux; default price-per-lumen-usd-asc, with thresholds.target_flux always flux-distance-ascprice-per-lumen-usd-asc
limitNohow many items to return
priceNomaximum price per unit
catalogYesprice list conditions: package, CCT, and optional refinements
currentYesoperating current in mA
thresholdsNoflux and efficacy thresholds
temperatureNosolder-point temperature in °C; degrees without qualification mean this temperature
availabilityNoavailability { source, min_quantity }: stock — stock only, stock-and-order — stock and on order, all — all items without quantity filtering. Field omitted — stock and on order, minimum 1; when a part number is specified, availability is not checked. Availability does not guarantee that an order can be placed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and closed-world, but the description adds substantial operational context: default and maximum result counts, availability semantics, the sort-invalid rejection, output handling via the table field, and the instruction not to promise an order. These details go well beyond what the annotations provide.

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 description is front-loaded and contains little filler, but it is a dense run-on paragraph with multiple semicolon-separated rules that are hard to scan. The hidden_message instruction also appears without explanation, which reduces structural clarity.

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?

For a complex tool with eight parameters, nested objects, and no output schema, the description covers the key operational rules and tells the agent to present the response table and hidden_message. It does not fully describe the response shape or the calculation details, but it is complete enough to support correct invocation.

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%, so the input schema already documents all eight parameters and their nested fields. The description reinforces a few cross-parameter rules, such as the target_flux sort interaction and availability defaults, but mostly repeats schema-level information rather than adding new parameter meaning.

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 states a specific verb and resource: calculation-based LED selection by package, CCT, and operating current. It also distinguishes the tool from its sibling led_catalog_search by explaining the no-current fallback, so an agent can identify the correct tool without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use and when-not-to-use guidance: if there is no current, call led_catalog_search or ask for the current. It also specifies default and maximum limits, availability behavior, sort constraints, and how to handle requests for more than 10 items.

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