10ML Perfume Finder

Suggest perfume layering

suggest_layering

Read-onlyIdempotent

Perfume 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).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many results per page (1-10, default 5).
`notes`	No	One or two notes. Examples: ["vanilla","citrus"], ["oud"]
`locale`	No	Language of the 10ml.com links and labels. Perfume, house and note names stay as they are.	en
`perfumes`	No	One or two perfumes. Examples: ["Parfums de Marly Delina"], ["Dior Sauvage","Creed Aventus"]
`response_format`	No	concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection).	concise

Output Schema

TableJSON 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.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful non-structural behavior: results are labeled 'editors' for editorial pairings vs 'suggested' for unvetted combinations that 'should be tested on skin', which tells the agent how to weight and caveat output. It does not discuss pagination or result counts beyond the schema's limit field.

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?

It is front-loaded with the core capability, followed by input modes, result labeling, example queries, and the exclusion. Every sentence serves a purpose, though the three inline example phrasings plus the input-mode enumeration make it denser than strictly necessary.

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 an output schema present, return values need not be described, and annotations cover the safety profile. The description still supplies the input-mode semantics and result-trust labeling an agent needs to call this correctly, leaving no obvious gap for a 5-parameter, zero-required tool.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the semantic consequence of each parameter choice — a single perfume yields 'partners from the index', two perfumes answer 'does this pair work' — which the schema's terse examples do not convey.

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 names the specific resource (perfume layering combinations) and states exactly what the tool returns: which notes/perfumes combine, what the combination smells like, spray order and amount, and when it suits. It also differentiates itself from the closest sibling by stating 'Not for choosing a single perfume (use recommend_perfumes).'

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 the four supported input shapes (two notes, one note, one perfume, two perfumes) and what each produces, then gives three concrete example queries. It explicitly names the alternative tool for the out-of-scope case (recommend_perfumes), so both when-to-use and when-not-to-use are 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.