Skip to main content
Glama

MadMax Trade Supply parts

Get product

get_product
Read-only

Full details for one SKU: price for the ship-to state, shipping, return window, auto-ship options, part numbers it replaces, and an add-to-cart URL.

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": {
      "sku": "<sku>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesMadMax SKU, e.g. MM-RF-891B5F
ship_to_zipNoOptional 5-digit ship-to ZIP; some regions add a shipping surcharge at checkout.
ship_to_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ship_to_zip
      Added value: +{
      +  "description": "Optional 5-digit ship-to ZIP; some regions add a shipping surcharge at checkout.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/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 and the description need only add lookup-specific behavior. It does add value by disclosing that price is resolved per ship-to state and that the response carries an add-to-cart URL, but it says nothing about behavior on an unknown or discontinued SKU, pagination, or whether the returned price includes tax.

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?

A single front-loaded sentence that spends its words entirely on the resource and the returned payload, with no filler or restatement of the title.

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 return values and does so thoroughly via the field enumeration. What remains thin is edge-case behavior for invalid SKUs and the precedence between the two location parameters, which is a modest gap for a simple read-only lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the one undocumented parameter, ship_to_state, is given meaning by the description's 'price for the ship-to state', which tells the agent that state drives pricing. Combined with the schema's own notes on SKU format and the ZIP surcharge, this leaves little ambiguity, though the interaction between ship_to_zip and ship_to_state is not clarified.

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 resource and scope ('Full details for one SKU') and enumerates the exact fields returned (price, shipping, return window, auto-ship, replacement part numbers, add-to-cart URL). That makes it clearly distinct from search_parts or get_store_policies, though it never names a sibling explicitly, which keeps it just below the top mark.

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: an agent can infer this is for a single known SKU rather than browsing or searching, largely because of the 'one SKU' phrasing and the required SKU parameter. There is no explicit when-to-use statement, no exclusions, and no pointer to an alternative such as search_parts when the SKU is unknown.

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