10ML Perfume Finder

Find a perfume gift

find_gift

Read-onlyIdempotent

Perfume gift ideas from who the gift is for: recipient (him, her or anyone), relationship, age range, perfumes or notes they already love, style, occasion and how adventurous to be. Each pick comes with the reason it suits them. Use for 'gift for a woman who loves Delina', 'something safe for my dad' or 'a bold present for a friend'. Not for personal taste recommendations (use recommend_perfumes) and not for classics lists (use search_perfumes with iconic true).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many results per page (1-12, default 5).
`loves`	No	Perfumes they already wear or love, e.g. ["Delina"]
`style`	No
`cursor`	No	next_cursor from the previous page; omit for the first page.
`locale`	No	Language of the 10ml.com links and labels. Perfume, house and note names stay as they are.	en
`boldness`	No	safe: crowd-pleasing classics; adventurous: distinctive niche picks	safe
`occasion`	No	When they would wear it most, e.g. "office"
`age_range`	No	Age range of the recipient
`recipient`	Yes	Who the gift is for: him (men and unisex), her (women and unisex) or anyone (unisex-friendly)
`liked_notes`	No	Notes they like, e.g. ["vanilla","rose"]
`relationship`	No	Example: "partner", "dad", "colleague", "friend"
`response_format`	No	concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection).	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tip`	Yes
`picks`	Yes
`total`	Yes
`source`	Yes
`message`	No
`unresolved`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 20, 2026
- 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 / picks / items / properties / perfume / properties / accords / description
```
Removed value: -"Main accords, strongest first"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / character / description
```
Removed value: -"One-sentence description by 10ML's fragrance editors"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / family / description
```
Removed value: -"Fragrance family, e.g. \"amber floral\""
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / id / description
```
Removed value: -"Stable Fragrance Index id, usable with get_perfume and find_similar_perfumes"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / key_notes / description
```
Removed value: -"The defining notes (empty when no pyramid is published)"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / links / description
```
Removed value: -"1-3 relevant 10ml.com links"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / links / items / properties / url / description
```
Removed value: -"A 10ml.com link in the requested locale"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / longevity / description
```
Removed value: -"1 (short) to 5 (very long)"
```
- removedOutput schema / properties / picks / 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 / picks / items / properties / perfume / properties / projection / description
```
Removed value: -"1 (skin scent) to 5 (fills a room)"
```
- removedOutput schema / properties / picks / items / properties / perfume / properties / year / description
```
Removed value: -"Launch year when known"
```
- removedOutput schema / properties / total / description
```
Removed value: -"How many results matched in all"
```

Changed2 schema fields changedOct 20, 2026

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

changedOutput schema / properties / picks / 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 / 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."

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 / picks / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / picks / items / properties / perfume / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / picks / items / properties / perfume / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / picks / items / properties / perfume / properties / pyramid / additionalProperties
```
Removed value: -false
```

AddedOct 19, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: each result arrives with the reason it suits the recipient, which tells the agent what the payload contains beyond raw matches. It does not discuss result volume or how paging interacts with the limit, keeping it short of a 5.

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

Conciseness5/5

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

Three sentences, front-loaded with what the tool returns, followed by trigger examples and then exclusions. No filler and nothing is repeated from the schema or annotations.

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?

For a 12-parameter tool with an output schema and rich annotations, the description supplies exactly the missing layer: purpose, usage triggers, sibling routing, and the shape of the returned reasoning. Nothing an agent needs in order to choose and call this tool 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 92%, so per-parameter documentation is largely handled by the schema and a baseline of 3 applies. The description nonetheless adds real semantic value by mapping a natural-language gift request onto the facet set (recipient, relationship, age range, loved perfumes/notes, style, occasion, boldness), showing how a vague human request decomposes into these inputs.

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 (perfume gift ideas) and immediately scopes it by the gift-recipient framing rather than personal taste. It explicitly names the siblings it is not (recommend_perfumes, search_perfumes with iconic true), so an agent can distinguish it without opening a schema.

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 concrete trigger examples ('gift for a woman who loves Delina', 'something safe for my dad', 'a bold present for a friend') plus explicit exclusions that route to recommend_perfumes for personal taste and search_perfumes for classics lists. 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.