Skip to main content
Glama

led_catalog_search

Read-only

Price list without calculation: catalog search without current; package and CCT are required, plus part number, voltage, CRI, quantity, availability, and price. Without availability — stock and on order only; availability.source=all — all items without quantity filtering. The response has no flux or lm/W — use led_select with an operating current for those. 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": {
      "package_size": "<package_size>",
      "color_temp": "<color_temp>"
    },
    "name": "led_catalog_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
criNocolor rendering index
priceNomaximum price per unit
markingNopart number or model
voltageNovoltage
color_tempYesCCT
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
min_quantityNoquantity specified by the user; 0 if not specified
package_sizeYesLED package

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing that the response omits flux/lm/W, that results should be rendered from the response `table` field, that hidden_message must be passed to the user, and that no order should be promised. These are operationally critical behaviors that no structured field conveys, especially with no output schema.

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?

It is short and front-loads the scoping statement, with no filler sentences. The heavy semicolon-and-dash chaining ("Without availability — stock and on order only") makes it denser than it needs to be and slightly harder to parse than a clean sentence structure would be.

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?

With no output schema and a nested availability object, the description correctly compensates by explaining the response shape (table field, absent flux) and presentation instructions. It leaves out edge cases such as empty results or result limits, which is a modest gap rather than a blocking one.

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 schema already documents every parameter including the availability source enum and its defaults. The description restates the required fields and the availability default but adds no new format or syntax detail beyond what the schema already provides, making the baseline 3 correct.

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 concrete verb+resource ("catalog search") and pins the scope as a price list without current calculation, requiring package and CCT. It distinguishes itself from the sibling by directing flux/lm/W lookups to led_select, though the opening phrase "Price list without calculation: catalog search without current" is telegraphic and takes a second read.

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

Usage Guidelines4/5

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

It gives an explicit routing rule to the alternative: use led_select with an operating current when flux or lm/W is needed, and it clarifies the default when availability is omitted (stock and on order). It does not state when this tool should be avoided beyond the flux case, so a 4 rather than a 5.

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