Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hermes_category

Browse a Hermès product category to get normalized product details, facet groups, and category info with fixed 48-item pages.

Instructions

Browse a Hermès category. Browses one Hermès product category and returns a page of normalized products (SKU, title, price with currency, colour, size, stock, images) plus the facet groups Hermès offers for that category, and the category's own title and description. The category parameter takes a category code from hermes-categories, which is the discovery endpoint for every accepted value. Page size is fixed at 48 by Hermès and cannot be changed. Prices are returned with the ISO-4217 currency for the selected market, since Hermès itself publishes bare numbers.

Input Schema

TableJSON 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
sortNoResult order. One of: relevance, priceasc, pricedsc. Non-default sorts are best-effort
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
categoryYesHermès category code, from hermes-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses fixed page size (48) and ISO-4217 currency handling, which are useful. However, it does not mention that pages beyond 1 are best-effort (though that is in the schema) or any rate limits/authentication. It adds some behavioral context but is not exhaustive.

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?

The description is three sentences with no fluff. It front-loads the purpose and then adds key constraints (page size, currency). It is efficient and well-structured.

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?

The description explains the output structure (normalized products, facets, category title/description) and important constraints (page size, currency). While it lacks explicit mention of best-effort pages or error conditions, those are partially covered in the schema. For a read-only browse tool, it is fairly complete.

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 all parameters. The description adds a little context, such as the category code source and page size, but these are also in the schema. It does not significantly enhance understanding of page, sort, or locale beyond what is already provided.

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?

The description clearly states it browses one Hermès product category and returns normalized products, facets, and category info. It distinguishes itself by referencing hermes-categories as the discovery endpoint for category codes, so an agent can tell it apart from related tools like hermes_products or hermes_search.

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?

It tells you to get the category code from hermes-categories, which is a useful prerequisite, but it does not explicitly state when to prefer this tool over siblings like hermes_search or hermes_products. The guidance is implied rather than explicit, with no exclusions or alternative recommendations.

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