Skip to main content
Glama

MadMax Trade Supply parts

What fits

check_fit
Read-only

Find the replacement we carry for an OEM part number (e.g. WF3CB, XWF, Aprilaire 35, LT700P), a nominal air filter size (e.g. 20x25x4) or a system/model name. Matching is based on our product titles.

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": "check_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOEM part number, filter size, or model/system name
ship_to_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 a genuinely useful caveat beyond that: matching is title-based, which tells the agent results are heuristic rather than a guaranteed cross-reference. It stops short of saying what happens on no match or how many candidates come back.

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 sentences, both earning their place: the first front-loads the purpose with inline examples, the second delivers the one behavioral caveat that matters. No filler, no restatement of the name or title.

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

Completeness3/5

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

For a low-complexity read-only tool with no output schema, the description covers input forms and matching basis but leaves two gaps an agent would want: the shape of the result (a single best match, a ranked list, a yes/no fit verdict, which the name 'check_fit' hints at) and the meaning of the undocumented `ship_to_state` 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?

With 50% schema coverage, the description must partly compensate. It does so well for `query` by supplying real example formats (WF3CB, XWF, Aprilaire 35, LT700P, 20x25x4) that go beyond the schema's generic wording, but `ship_to_state` is left entirely unexplained in both the schema and the description, leaving its role (availability? shipping estimate?) opaque.

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?

States a specific verb and resource ('Find the replacement we carry for...') and enumerates the three input classes it accepts (OEM part number, nominal size, model/system name) with concrete examples. It does not explicitly distinguish itself from sibling search_parts, so an agent must infer the split between 'find replacement' and 'search parts' on its own.

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?

Usage is only implied by the input examples: call it when you hold an OEM number or a filter size and want the equivalent we stock. There is no statement of when not to use it, no mention of the sibling search_parts as the alternative for keyword browsing, and no guidance on what to do with an ambiguous or unmatched query.

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