MaxGaming MCP Server

Overview Schema Source Related Servers Discussions Admin

search_products

Search a selected MaxGaming storefront by keywords, model number, or term, and filter results by brand, price, and availability with optional sorting and detailed product data.

Instructions

Search the selected MaxGaming storefront. Results and total_products may include products unrelated to the query. Brand, price and availability filters are applied locally per page. Sort order and include_details are optional. Use get_product for exact URLs or article numbers.

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

Name	Required	Description	Default
`page`	No	Results page, starting at 1. Use next_page to continue.
`brand`	No	Filter by brand name (applied locally per page).
`fresh`	No	Bypass the process cache and request current shop data.
`query`	Yes	Product keywords, model number, or search term.
`country`	No	Storefront country code. Defaults to us (International).	us
`language`	No	Shop language; defaults to the country's language. MaxGaming uses one language per storefront.
`order_by`	No	Sort order: '' (recommended), 'DisplayName-Asc', 'DisplayName-Desc', 'SalesPrice-Asc', 'SalesPrice-Desc'.
`max_price`	No	Maximum price in the local currency (applied locally per page).
`min_price`	No	Minimum price in the local currency (applied locally per page).
`availability`	No	Filter by availability text, e.g. 'In stock', 'Pre-order', 'Out of stock' (applied locally per page).
`include_details`	No	Fetch each product page to include full details, variants and specifications. Slower.

Output Schema

Name	Required	Default
`note`	No
`page`	Yes
`cache`	No
`count`	Yes
`query`	Yes
`paging`	Yes
`source`	Yes
`country`	No	us
`coverage`	Yes
`language`	No	en
`products`	Yes
`retailer`	Yes
`next_page`	Yes
`observed_at`	No
`local_filters`	No
`related_pages`	No
`redirected_url`	No
`total_products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it warns results may include unrelated products, that filters apply only locally per page (so they are unreliable across pagination), that include_details is slower, and that fresh bypasses the cache. Missing only operational details like auth or rate limits.

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?

Five short sentences, front-loaded with the search intent and the caveat about unrelated results. The sentence about sort order and include_details being optional adds little beyond the schema defaults, a minor bit of dead weight.

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 an 11-parameter tool with a rich output schema, the description covers the non-obvious behavior and the main alternative. It leaves out authentication requirements and rate limits, which would matter for an unannotated search tool.

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 100%, so baseline is 3, but the description adds genuine meaning: it explains that the filtering parameters are applied locally per page rather than server-side, which changes how results should be interpreted. The note that order_by and include_details are optional is redundant with schema defaults.

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: search the selected MaxGaming storefront for products. It also names the sibling get_product and the condition that selects it (exact URLs or article numbers), so an agent can distinguish the two 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?

Gives explicit routing guidance to get_product and clarifies that brand/price/availability filters are local per page, which is a real usage constraint. It does not address when to use browse_page or list_storefronts, so it stops short of full alternative coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server