10ML Perfume Finder

Pick perfumes for an occasion

pick_for_occasion

Read-onlyIdempotent

Perfume picks for a moment: a season, an occasion (daytime, office, casual, evening, date night, special occasion), an audience and a style, each with the reason it fits. Use for 'a fresh summer office scent for men', 'date night perfume for her' or 'what to wear to a winter wedding'. Give at least one of season, occasion, gender or style. Not for taste-based matching (use recommend_perfumes), not for gifts (use find_gift) and not for classics (use search_perfumes with iconic true).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many results per page (1-15, default 6).
`style`	No	Styles wanted, e.g. ["fresh","clean"] for summer office wear
`cursor`	No	next_cursor from the previous page; omit for the first page.
`gender`	No	Audience the perfume is marketed to. men and women also include unisex perfumes.
`locale`	No	Language of the 10ml.com links and labels. Perfume, house and note names stay as they are.	en
`season`	No	Season the perfume suits (fall is accepted in text queries as autumn).
`occasion`	No	Occasion the perfume suits: daytime, office, casual, evening, date night or special occasion.
`response_format`	No	concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection).	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`picks`	Yes
`total`	Yes
`guides`	No
`source`	Yes
`filters`	Yes
`message`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 20, 2026
- removedOutput schema / properties / guides / 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 / 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"
+]

Changed11 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 / guides / items / 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 a safe, idempotent, closed-world read (readOnlyHint=true, idempotentHint=true, openWorldHint=false, destructiveHint=false), so the safety profile is covered. The description adds genuine value beyond that: results come 'each with the reason it fits', and it imposes an input constraint ('at least one of season, occasion, gender or style') that is not visible in the annotations. It stops short of describing pagination or result-shape behavior.

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 the core purpose, then examples, then exclusions. Every clause earns its place: the examples anchor the abstract categories, and the exclusion clause prevents the most likely misroutes. No filler.

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 no explanation, and the description covers what remains: purpose, valid inputs, an input precondition, and explicit sibling routing. For an 8-parameter, zero-required tool this leaves nothing an agent needs unresolved.

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% with enums documented inline, so the baseline is 3 and the schema carries the field-level detail. The description still adds a cross-parameter constraint the schema cannot express - at least one of season, occasion, gender or style must be supplied - which meaningfully guides parameter filling.

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 picks for a moment') and enumerates the dimensions that drive the pick (season, occasion, audience, style), each returned with its rationale. It also distinguishes itself from three named siblings, so an agent can separate it from recommend_perfumes, find_gift and search_perfumes without opening any 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 example queries ('a fresh summer office scent for men', 'date night perfume for her', 'what to wear to a winter wedding') plus the input precondition 'Give at least one of season, occasion, gender or style'. It explicitly names when NOT to use it and routes each case to the correct alternative (recommend_perfumes for taste, find_gift for gifts, search_perfumes with iconic true for classics).

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.