10ML Perfume Finder

Suggest perfume layering

suggest_layering

Read-onlyIdempotent

Perfume and fragrance layering ideas: which notes or perfumes combine well, what the combination smells like, how to spray (order, amount) and when it suits. Works from two notes ('vanilla and citrus'), one note (what it layers with), one perfume (partners from the index) or two perfumes (does this pair work). Editorial pairings are marked 'editors'; others are marked 'suggested' and should be tested on skin. Use for 'how do I layer vanilla', 'can I layer Delina with something', 'does Sauvage layer with Aventus'. Not for choosing a single perfume (use recommend_perfumes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_layering"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Results per page.
`notes`	No	One or two notes. Examples: ["vanilla","citrus"], ["oud"]
`locale`	No	Language of the 10ml.com links and labels.	en
`perfumes`	No	One or two perfumes. Examples: ["Parfums de Marly Delina"], ["Dior Sauvage","Creed Aventus"]
`response_format`	No	concise (default) or detailed (adds pyramid, seasons, occasions, longevity).	concise

Output Schema

Name	Required	Description	Default
`mode`	Yes
`pairs`	Yes
`advice`	Yes
`source`	Yes
`message`	No
`verdict`	No
`partners`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "ro",
-  "el",
-  "hu",
-  "cs",
-  "pl",
-  "nl"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "ro",
+  "el",
+  "hu",
+  "cs",
+  "pl",
+  "nl",
+  "pt",
+  "sv",
+  "da",
+  "fi",
+  "bg",
+  "hr"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "ro",
-  "el",
-  "hu",
-  "cs",
-  "pl"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "ro",
+  "el",
+  "hu",
+  "cs",
+  "pl",
+  "nl"
+]

Changed7 schema fields changedOct 21, 2026

changedInput schema / properties / limit / description

Previous value: -"How many results per page (1-10, default 5)."New value: +"Results per page."

changedInput schema / properties / locale / description

Previous value: -"Language of the 10ml.com links and labels. Perfume, house and note names stay as they are."New value: +"Language of the 10ml.com links and labels."

changedInput schema / properties / response_format / description

Previous value: -"concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection)."New value: +"concise (default) or detailed (adds pyramid, seasons, occasions, longevity)."

removedOutput schema / properties / pairs / items / properties

Removed value: -{
-  "best_for": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "notes": {
-    "additionalItems": false,
-    "items": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "string"
-      }
-    ],
-    "maxItems": 2,
-    "minItems": 2,
-    "type": "array"
-  },
-  "result": {
-    "type": "string"
-  },
-  "source": {
-    "enum": [
-      "editors",
-      "suggested"
-    ],
-    "type": "string"
-  },
-  "tip": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / pairs / items / required

Removed value: -[
-  "notes",
-  "result",
-  "tip",
-  "best_for",
-  "source"
-]

removedOutput schema / properties / partners / items / properties

Removed value: -{
-  "perfume": {
-    "properties": {
-      "accords": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "character": {
-        "type": "string"
-      },
-      "concentration": {
-        "type": "string"
-      },
-      "family": {
-        "type": "string"
-      },
-      "gender": {
-        "enum": [
-          "men",
-          "women",
-          "unisex"
-        ],
-        "type": "string"
-      },
-      "house": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "key_notes": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "links": {
-        "items": {
-          "properties": {
-            "title": {
-              "type": "string"
-            },
-            "type": {
-              "enum": [
-                "try",
-                "guide",
-                "note"
-              ],
-              "type": "string"
-            },
-            "url": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "type",
-            "title",
-            "url"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "longevity": {
-        "type": "number"
-      },
-      "name": {
-        "type": "string"
-      },
-      "occasions": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "other_versions": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "perfumers": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "profile": {
-        "enum": [
-          "full",
-          "core"
-        ],
-        "type": "string"
-      },
-      "projection": {
-        "type": "number"
-      },
-      "pyramid": {
-        "properties": {
-          "base": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "heart": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "top": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "required": [
-          "top",
-          "heart",
-          "base"
-        ],
-        "type": "object"
-      },
-      "seasons": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "styles": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "year": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "house",
-      "gender",
-      "family",
-      "accords",
-      "key_notes",
-      "character",
-      "links",
-      "profile"
-    ],
-    "type": "object"
-  },
-  "via": {
-    "type": "string"
-  },
-  "why": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / partners / items / required
```
Removed value: -[
-  "perfume",
-  "via",
-  "why"
-]
```

Changed11 schema fields changedOct 20, 2026
- removedOutput schema / properties / partners / items / properties / perfume / properties / accords / description
```
Removed value: -"Main accords, strongest first"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / character / description
```
Removed value: -"One-sentence description by 10ML's fragrance editors"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / family / description
```
Removed value: -"Fragrance family, e.g. \"amber floral\""
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / id / description
```
Removed value: -"Stable Fragrance Index id, usable with get_perfume and find_similar_perfumes"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / key_notes / description
```
Removed value: -"The defining notes (empty when no pyramid is published)"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / links / description
```
Removed value: -"1-3 relevant 10ml.com links"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / links / items / properties / url / description
```
Removed value: -"A 10ml.com link in the requested locale"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / longevity / description
```
Removed value: -"1 (short) to 5 (very long)"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / other_versions / description
```
Removed value: -"Ids of other concentrations or flankers of the same perfume in the index"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / projection / description
```
Removed value: -"1 (skin scent) to 5 (fills a room)"
```
- removedOutput schema / properties / partners / items / properties / perfume / properties / year / description
```
Removed value: -"Launch year when known"
```

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / partners / items / properties / perfume / properties / profile
```
Added value: +{
+  "enum": [
+    "full",
+    "core"
+  ],
+  "type": "string"
+}
```

changedOutput schema / properties / partners / items / properties / perfume / required

Previous value: -[
-  "id",
-  "name",
-  "house",
-  "gender",
-  "family",
-  "accords",
-  "key_notes",
-  "character",
-  "links"
-]New value: +[
+  "id",
+  "name",
+  "house",
+  "gender",
+  "family",
+  "accords",
+  "key_notes",
+  "character",
+  "links",
+  "profile"
+]

Changed10 schema fields changedOct 19, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / locale / description

Previous value: -"Language of the 10ml.com links and fixed labels: en, de, fr, es, it, ro, el, hu, cs or pl. Perfume, house and note names are never translated."New value: +"Language of the 10ml.com links and labels. Perfume, house and note names stay as they are."

changedInput schema / properties / response_format / description

Previous value: -"concise (default): the essentials, about a third of the size. detailed: adds the full note pyramid, seasons, occasions, longevity and projection."New value: +"concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection)."

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / pairs / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / partners / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / partners / items / properties / perfume / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / partners / items / properties / perfume / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / partners / items / properties / perfume / properties / pyramid / additionalProperties
```
Removed value: -false
```

AddedOct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new behavioral context: results are labeled 'editors' for editorial pairings versus 'suggested' for untested ones that should be tried on skin. That provenance/signal distinction affects how the agent should present results. It does not describe pagination behavior, though the limit param and output schema cover that.

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?

Densely front-loaded: purpose, accepted input forms, result labeling, and the sibling hand-off all appear in one paragraph with no filler. The single run-on sentence packs several ideas together, which slightly reduces skimmability but every clause carries information.

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 annotations covering safety, an output schema covering return shape, and full schema coverage on all five parameters, the description supplies the remaining missing layer: input-mode routing, example queries, result-reliability labeling, and the alternative tool. Nothing an agent needs in order to call this correctly is absent.

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 meaning beyond the schema by mapping natural-language asks to the notes vs perfumes parameter modes and clarifying that a single value yields partners from the index while two values yield a compatibility judgement. It does not touch limit, locale, or response_format, which is acceptable since the schema documents them.

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 and resource (suggest perfume layering ideas) and enumerates the four input shapes it accepts — two notes, one note, one perfume, two perfumes — so the agent knows exactly what the tool consumes. It also names the sibling it is not (recommend_perfumes), making it distinguishable 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?

Gives explicit trigger phrasings ('how do I layer vanilla', 'can I layer Delina with something', 'does Sauvage layer with Aventus') plus an explicit exclusion routing to recommend_perfumes for single-perfume choice. When-to-use and when-not-to-use are both covered.

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

All 10ML Perfume Finder 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.