Skip to main content
Glama

La Luer — AI Skincare Commerce

skincare_recommend

Read-only

(Deprecated: use 'recommend' instead. Works identically.) Get a personalized La Luer product recommendation with ingredient-aware scoring and routine building. Use when the user wants advice on what to buy, needs help choosing between products, has a specific skin concern (acne, aging, dryness, sensitivity, etc.), wants a routine, or asks "what should I use for X." Do not use for browsing or listing products — use search_products instead. Returns scored products with explanations, usage instructions, and Shopify checkout. This tool analyzes ingredients and product compatibility — use it over search_products when the user needs guidance, not just a product list.

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": "skincare_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoFilter to a specific brand only (e.g. 'Glossier', 'CeraVe', 'The Ordinary'). Use when the user asks for products from a specific brand.
queryYesNatural language query about skin concerns (e.g. 'I have oily acne-prone skin, under $30')
strategyNoOptional offer strategy override: starter, gentle, budget, glow_safe, minimal, strong, fallback

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural language query about skin concerns (e.g. 'I have oily acne-prone skin and want something gentle under $30')"New value: +"Natural language query about skin concerns (e.g. 'I have oily acne-prone skin, under $30')"
  2. Changed1 schema field changed
    • changedInput schema / properties / brand / description
      Previous value: -"Filter to a specific brand only (e.g. 'Youth to the People', 'CeraVe', 'The Ordinary'). Use when the user asks for products from a specific brand."New value: +"Filter to a specific brand only (e.g. 'Glossier', 'CeraVe', 'The Ordinary'). Use when the user asks for products from a specific brand."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: it analyzes ingredients and compatibility, returns scored products with explanations and usage instructions, and surfaces Shopify checkout. It does not mention pagination, latency, or result counts, but the added detail is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the deprecation notice, which is good, but the usage guidance is duplicated: the 'use it over search_products when the user needs guidance' sentence restates the earlier 'Do not use for browsing... use search_products instead' instruction. Trimming that final sentence would tighten the definition without losing meaning.

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?

There is no output schema, and the description compensates by describing what comes back (scored products, explanations, usage instructions, checkout). Combined with full annotation coverage and complete parameter docs, an agent has enough to call it correctly; only edge-case behavior (empty results, validation limits) is unaddressed.

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, brand, and strategy with examples, and the description adds nothing parameter-specific beyond a generic mention of skin-concern queries. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 gives a specific verb and resource ('Get a personalized La Luer product recommendation with ingredient-aware scoring and routine building') and explicitly distinguishes itself from search_products. The deprecation pointer to 'recommend' is stated up front, so the agent immediately knows the tool's identity and status.

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?

It enumerates precise triggering conditions (advice on what to buy, choosing between products, a specific skin concern, wanting a routine, 'what should I use for X') and an explicit exclusion with an alternative ('Do not use for browsing or listing products — use search_products instead'). The deprecated-in-favor-of-'recommend' note adds another routing rule.

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