10ML Perfume Finder

Explain a note

explain_note

Read-onlyIdempotent

Explain a fragrance note: what it smells like, its family and mood, where it comes from, which notes it pairs with, similar notes, famous perfumes where it leads and a link to the 10ML note page or guide when one exists. Covers about 285 notes in many spellings and languages. Use for 'what does ambroxan smell like', 'what is oud', 'what goes with bergamot'. Not for listing every perfume with the note (use perfumes_by_note) and not for general terms like EDP or sillage (use explain_perfume_term).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes	The note. Examples: "ambroxan", "oud", "iris", "orris", "Bergamotte"
`locale`	No	Language of the 10ml.com links and labels. Perfume, house and note names stay as they are.	en
`response_format`	No	concise (default) or detailed (adds note pyramid, seasons, occasions, longevity, projection).	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`found`	Yes
`links`	No
`source`	Yes
`message`	No
`suggestions`	No
`famous_perfumes`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / famous_perfumes / items / properties / profile

Added value: +{
+  "enum": [
+    "full",
+    "core"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / famous_perfumes / items / 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 / famous_perfumes / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / famous_perfumes / items / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / famous_perfumes / items / properties / pyramid / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / note / 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the returned content structure and the breadth/limitation of the knowledge base (roughly 285 notes, multiple spellings and languages, link only when one exists), which tells the agent what it can and cannot expect from a lookup.

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 return contents, then examples, then exclusions, so the most decision-relevant information comes first. The content enumeration is long but each clause maps to a distinct returned field, so little is wasted; only slight trimming is possible.

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 the description need not explain return values, yet it still summarizes them, and annotations cover the safety profile. Combined with explicit alternatives and trigger examples, an agent has everything needed to select and invoke the tool correctly.

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%, with enum values and defaults documented for locale and response_format, so the schema does the heavy lifting. The description adds only marginal parameter context, implying the link target depends on locale; it does not clarify note spelling tolerance or detailed-vs-concise trade-offs beyond the schema text.

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 opens with a specific verb+resource ('Explain a fragrance note') and then enumerates exactly what the explanation covers: smell, family, mood, origin, pairings, similar notes, leading perfumes, and a page link. It also states coverage scope (about 285 notes in many spellings and languages), so an agent knows the tool's reach 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?

It gives explicit trigger queries ('what does ambroxan smell like', 'what is oud', 'what goes with bergamot') and two named exclusions with the correct alternative for each: perfumes_by_note for listing perfumes with the note, and explain_perfume_term for general terms like EDP or sillage. Nothing is left to inference.

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.