Vesremont

search_products

Read-onlyIdempotent

Find or browse current catalog products by name, model or SKU; returns a bounded page with an exact total. Get contextual filter IDs from get_catalog_filters and brand IDs from search_brands; do not guess IDs. Read a selected result with get_product; narrow overly broad queries. Public; no OAuth required. Read-only.

Input Schema

Name	Required	Description
`q`	No	Storefront text search query. Omit to browse the catalog with the supplied section, brand and filters.
`page`	No	One-based result page, default 1. Do not combine with cursor; the existing offset window still applies.
`sort`	No	Catalog order: id_sort is the default ID order; price_min sorts cheapest first, price_max most expensive first.
`cursor`	No	Opaque next_cursor from the previous response. Keep the same filters/sort; do not combine with page. Expires after 15 minutes. Existing backend windows apply; not a frozen snapshot.
`filters`	No	Storefront catalog filters. Combine with the current section/brand context; REST encodes this object as one JSON query value.
`brand_id`	No	Restrict to this brand ID returned by search_brands or product data, not its display name.
`per_page`	No	Maximum results per page, default 20. Keep the same value when following next_cursor.
`section_id`	No	Restrict to this real catalog section. Do not combine with filters.section_ids.

Output Schema

Name	Required	Description	Default
`items`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / items / items / properties / gtin

Added value: +{
+  "anyOf": [
+    {
+      "description": "Barcode from the published catalog field, if present. Not a product ID and not inferred from the name or URL.",
+      "pattern": "^(?:[0-9]{8}|[0-9]{12,14})$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world. The description adds useful context beyond them: public access with no OAuth required, and that results come as a bounded page with an exact total. It does not add much on failure modes or rate limits, but the annotation bar is already met.

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?

Three tightly packed sentences, front-loaded with purpose and then the cross-tool workflow. Every clause carries actionable information with no filler.

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

Completeness5/5

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

With a rich schema, full annotations, and an output schema present, the description covers the remaining gap: cross-tool ID sourcing, browse-vs-search behavior, and auth profile. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and each parameter (q, page, sort, cursor, filters, brand_id, per_page, section_id) is thoroughly documented in the schema itself. The description reinforces the 'do not guess IDs' workflow but adds little parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs (find/browse), the resource (current catalog products), and the search keys (name, model, SKU). It also names the sibling tools it works with (get_catalog_filters, search_brands, get_product), so an agent can distinguish it from other retrieval tools without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: get filter IDs from get_catalog_filters, brand IDs from search_brands, do not guess IDs, read a selected result with get_product, and narrow overly broad queries. This is clear when-to-use plus named alternatives, which is the top bar.

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

All Vesremont tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?