Skip to main content
Glama

MadMax Trade Supply parts

Search parts

search_parts
Read-only

Search MadMax Trade Supply's in-stock catalog (refrigerator and water filters, HVAC air filters, humidifier pads, sump and septic alarms/parts, radon mitigation parts, batteries, LED bulbs, pool and spa filters) by keyword, OEM part number, filter size (e.g. 16x25x1) or brand. Returns live USD prices for the ship-to state.

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_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeywords, OEM part number, or filter size
categoryNoOptional category slug (see list_categories)
max_priceNo
ship_to_stateNo2-letter US state/territory code; prices vary slightly by state. Default MN.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are restricted to in-stock items and prices are live USD values that vary by ship-to state, which an agent needs to interpret results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler; the catalog scope and search modes come first, followed by the return-value note. Every clause carries information.

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, the description carries the burden of describing returns and does so at a high level (live USD prices, in-stock catalog). Minor gaps remain around result shape and pagination behavior via limit, but the essentials for correct invocation are present.

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?

The description adds real meaning for query (keyword, OEM number, filter size, brand) and explains that ship_to_state drives price variation, which the schema also notes. It says nothing about limit, max_price, or category beyond what the schema already provides, and coverage is only 60%.

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 verb (search) and resource (MadMax Trade Supply's in-stock catalog) and enumerates the product families and search modes (keyword, OEM part number, filter size, brand). It is clearly a catalog search, distinguishable in spirit from get_product, though it never names a sibling explicitly.

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?

It conveys the contexts in which the tool is useful (finding parts by keyword, OEM number, size, or brand) and that results are in-stock with live pricing. It gives no explicit when-not guidance or pointer to alternatives such as get_product for a known item or check_fit for compatibility.

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