Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

hermes_search

Search the Hermès catalogue by keyword and return product results as JSON; unmatched queries return zero products, with spelling corrections reported in results_for.

Instructions

Search the Hermès catalogue. Searches the Hermès catalogue by keyword and returns a page of products in the same shape as hermes-category. A query Hermès has no match for returns total 0 with an empty products array: Hermès itself renders unrelated fallback recommendations on a no-results page, and those are deliberately not returned as results. When Hermès applies its own spelling correction the corrected term is reported in results_for. Page size is fixed at 48 by Hermès and cannot be changed.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page; page size is fixed at 48. Page 1 is fully validated; pages beyond 1 are best-effort and provisional
queryYesSearch keyword
localeNoMarket and language. One of: at_de, au_en, be_en, be_fr, br_pt, ca_en, ca_fr, ch_de, ch_fr, cz_en, de_de, dh_en, dk_en, es_es, fi_en, fr_fr, gr_en, hk_en, ie_en, it_it, jp_ja, kr_ko, lu_fr, mo_en, mx_es, my_en, nl_en, no_en, pl_en, pt_en, ri_en, se_en, sg_en, th_en, tw_zh, uk_en, us_en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it fixes page size at 48, states that no-match queries return total 0 with an empty array and deliberately omit Hermès fallback recommendations, and notes that spelling corrections surface in results_for. These are non-obvious behaviors an agent could otherwise misinterpret. It doesn't touch auth or rate limits, keeping it short of a 5.

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?

Front-loaded with the core action, then layers in the important edge cases. The opening two sentences ('Search the Hermès catalogue. Searches the Hermès catalogue by keyword...') are mildly redundant, but the rest is dense and earns its place.

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 does the necessary work of describing the return shape (mirrors hermes-category), the empty-result contract, and the results_for correction field, plus pagination limits. Complete enough for correct invocation, though it omits any notion of result ordering or fields.

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%, so the schema already documents query, page, and locale, including the best-effort caveat for pages beyond 1. The description only re-states the fixed 48 page size and adds nothing new about query or locale syntax, 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 a specific verb (search) and resource (the Hermès catalogue), and pins the output shape by reference to a named sibling (hermes-category). An agent can immediately tell it does keyword product search and even knows the return shape family.

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 description explains no-match behavior and points to hermes-category for output shape, but it never states when to prefer hermes_search over siblings like hermes_suggest or hermes_category/category browsing. Usage is implied rather than prescribed.

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

Deploy Server

Other Tools