Skip to main content
Glama

MaterialHandling.com

search_products

Search the MaterialHandling.com catalog (38,000+ industrial products: lift tables, pallet jacks, casters, dock equipment, hoists, cranes, carts, shelving and more from Vestil, Valley Craft and other brands). Returns name, SKU, price, availability, lead time (business days) and product URL. Use get_product for full specs.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-25 (default 10)
queryYesSearch terms, e.g. "electric lift table 2000 lbs" or a SKU/model number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the return fields (name, SKU, price, availability, lead time in business days, product URL), which is genuinely useful. However, it says nothing about whether the call is read-only, any authentication or rate-limit constraints, or what happens with zero matches — gaps that matter for a public catalog search.

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?

Three sentences, front-loaded with the catalog scope, then returns, then the sibling hand-off — a logical order with no filler. The parenthetical product/brand list is the one place it runs long, though it does help the agent form query terms.

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 two-parameter, read-only style search with no output schema, the description covers scope, return fields, and the escalation path to get_product. Only minor items are missing — zero-result behavior and result-order/pagination semantics beyond the limit parameter.

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 coverage is 100%, so both parameters are already documented, including the SKU/model-number usage and the 1-25 limit range. The description adds only indirect query-shaping context via the product-category enumeration; it does not add syntax or matching-behavior detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (search) and resource (MaterialHandling.com catalog), with the catalog scope quantified (38,000+ industrial products) and product families enumerated. It also explicitly distinguishes itself from get_product, so an agent can route between search and detail lookup without opening either schema.

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?

Names the alternative — get_product for full specs — which tells the agent when this summary-level search is enough versus when to drill in. It lacks an explicit negative case (e.g. use get_categories for browsing without a query term), so routing to that sibling is left to inference.

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