10ML Perfume Finder

Find perfume alternatives

find_perfume_alternatives

Read-onlyIdempotent

The editors' alternatives (dupes) to a famous perfume or cologne, from other houses: for each, why it is close and how close (very close, similar vibe, same spirit), plus the 10ML guide that compares them. Covers about 100 iconic originals such as Creed Aventus, Baccarat Rouge 540, Delina, Sauvage, Black Opium or Santal 33. For other fragrances in the index the closest options from different houses are computed from notes and accords. Use for 'dupe of X', 'alternative to X', 'what smells like X from another house'. Not for general similarity inside the index (use find_similar_perfumes) and not for free-text discovery (use search_perfumes).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`house`	No	House of the original when the name is ambiguous, e.g. "Parfums de Marly"
`limit`	No	Results per page.
`cursor`	No	next_cursor from the previous page.
`locale`	No	Language of the 10ml.com links and labels.	en
`perfume`	Yes	The famous perfume to find alternatives for. Examples: "Creed Aventus", "Baccarat Rouge 540", "Delina"
`closeness`	No	Only alternatives at this closeness

Output Schema

TableJSON Schema

Name	Required	Description	Default
`guide`	No
`links`	Yes
`total`	Yes
`source`	Yes
`message`	No
`original`	Yes
`next_cursor`	No
`alternatives`	Yes
`other_matches`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 21, 2026

changedInput schema / properties / cursor / description

Previous value: -"next_cursor from the previous page; omit for the first page."New value: +"next_cursor from the previous page."

changedInput schema / properties / limit / description

Previous value: -"How many results per page (1-10, default 6)."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."

removedOutput schema / properties / alternatives / items / properties

Removed value: -{
-  "closeness": {
-    "enum": [
-      "very close",
-      "similar vibe",
-      "same spirit"
-    ],
-    "type": "string"
-  },
-  "house": {
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "name": {
-    "type": "string"
-  },
-  "source": {
-    "enum": [
-      "editors",
-      "similarity"
-    ],
-    "type": "string"
-  },
-  "why": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / alternatives / items / required

Removed value: -[
-  "name",
-  "closeness",
-  "why",
-  "source"
-]

removedOutput schema / properties / guide / properties

Removed value: -{
-  "title": {
-    "type": "string"
-  },
-  "type": {
-    "enum": [
-      "try",
-      "guide",
-      "note"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / guide / required

Removed value: -[
-  "type",
-  "title",
-  "url"
-]

removedOutput schema / properties / links / items / properties

Removed value: -{
-  "title": {
-    "type": "string"
-  },
-  "type": {
-    "enum": [
-      "try",
-      "guide",
-      "note"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / links / items / required
```
Removed value: -[
-  "type",
-  "title",
-  "url"
-]
```

removedOutput schema / properties / original / properties

Removed value: -{
-  "house": {
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "name": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / original / required
```
Removed value: -[
-  "name"
-]
```

Changed8 schema fields changedOct 20, 2026
- removedOutput schema / properties / alternatives / items / properties / id / description
```
Removed value: -"Fragrance Index id when the alternative has its own profile"
```
- removedOutput schema / properties / guide / description
```
Removed value: -"The 10ML guide comparing this perfume with its alternatives"
```
- removedOutput schema / properties / guide / properties / url / description
```
Removed value: -"A 10ml.com link in the requested locale"
```
- removedOutput schema / properties / links / items / properties / url / description
```
Removed value: -"A 10ml.com link in the requested locale"
```
- removedOutput schema / properties / message / description
```
Removed value: -"Guidance when the result is empty, partial or needs a follow-up tool"
```
- removedOutput schema / properties / next_cursor / description
```
Removed value: -"Pass as cursor to get the next page; absent on the last page"
```
- removedOutput schema / properties / other_matches / description
```
Removed value: -"Other originals the query could also mean"
```
- removedOutput schema / properties / total / description
```
Removed value: -"How many results matched in all"
```

Changed9 schema fields changedOct 19, 2026

removedInput schema / $schema

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

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor from a previous result's next_cursor, to fetch the next page. Omit for the first page."New value: +"next_cursor from the previous page; omit for the first page."

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

removedOutput schema / $schema

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

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / alternatives / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / guide / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / original / additionalProperties
```
Removed value: -false
```

AddedOct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing a two-tier data model: ~100 curated iconic originals get editorial comparisons with closeness ratings, while other fragrances get computed note/accord-based options. It also enumerates the closeness buckets. It stops short of describing pagination or result shape, but the output schema covers returns.

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 purpose and capably organized into what-it-returns, coverage, and routing. Slightly dense first sentence with stacked parentheticals, but no sentence is wasted.

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?

Given an output schema, full annotation coverage, and 100% schema descriptions, the remaining burden is scope and data-source behavior, both of which are stated (curated set size, computed fallback, ambiguity handling via house). Nothing needed to call it correctly is missing.

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 house, limit, cursor, locale, and perfume are already self-documenting. The description adds only mild value: 'from other houses' clarifies the scope and it echoes the closeness vocabulary, but it does not define what 'similar vibe' vs 'same spirit' actually means.

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?

Specific verb+resource: it returns editor-curated 'dupes' from other houses for a named original, and it distinguishes itself from find_similar_perfumes and search_perfumes by name. An agent can tell exactly what this returns versus its siblings.

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?

Provides literal trigger phrases ('dupe of X', 'alternative to X', 'what smells like X from another house') and explicit exclusions pointing to the correct alternatives for in-index similarity and free-text discovery.

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.