Skip to main content
Glama

MadMax Trade Supply parts

Report a missing part or blocker

submit_feedback

Tell MadMax Trade Supply about a part you couldn't find, a fit question, a checkout problem or wrong data. A person reviews every report; nothing is sent back automatically and no order is placed. Leave contact_email only if the shopper wants a reply.

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
typeYes
queryNoThe search you ran
messageYesWhat was needed or what went wrong
agent_nameNoYour agent or app name
part_numberNoOEM part or model number searched for
contact_emailNoOptional, only with the shopper's consent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare write/not-destructive flags; the description adds substantive facts an agent could not infer: every report is human-reviewed, nothing is auto-returned, and no order is placed. The remaining gap is that idempotentHint=false is not surfaced — duplicate submissions presumably create duplicate reports, and that is not stated.

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, zero filler: purpose first, then post-submission behavior and the consent caveat. Every clause carries information an agent needs.

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 7-parameter, non-idempotent write tool with no output schema, the description covers the essential unknowns — human review, no order creation, no automatic reply, email consent. Only the duplicate-report behavior and any confirmation the caller receives are unaddressed, which is a minor omission given no output schema exists.

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 71%, so most parameters are already documented; the description only adds meaning for `contact_email` ("only if the shopper wants a reply"), which usefully encodes consent. It says nothing about how `sku`, `query`, or `part_number` differ in routing the report, leaving the remaining gap unaddressed.

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?

"Tell MadMax Trade Supply about a part you couldn't find, a fit question, a checkout problem or wrong data" gives a specific verb plus an enumerated set of report types that map directly to the `type` enum. It is clearly the escalation outlet rather than a lookup tool like search_parts or check_fit, though it never names those siblings 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?

The categories imply when to call it (when the shopper hits a dead end), but there is no explicit statement such as "use this instead of retrying search_parts" or a when-not condition. The second sentence explains what happens after submission rather than when to choose this tool.

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