10ML Perfume Finder

Get perfume house

get_house

Read-onlyIdempotent

Profile of a perfume house: country, founded year, style (designer, niche, Middle Eastern, indie), what it is known for, its signature perfumes in the index and a link to explore it at 10ML. Understands nicknames (YSL, MFK, PDM, Paco Rabanne). Use for 'tell me about Creed', 'what is Amouage known for' or 'best Dior perfumes'. Not for browsing all houses (use list_houses) and not for one perfume (use get_perfume).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`house`	Yes	The house. Examples: "Creed", "YSL", "Maison Francis Kurkdjian", "Parfums de Marly"
`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
`found`	Yes
`house`	No
`links`	No
`source`	Yes
`message`	No
`suggestions`	No
`signature_perfumes`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / signature_perfumes / items / properties / profile

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

changedOutput schema / properties / signature_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 / house / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / signature_perfumes / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / signature_perfumes / items / properties / links / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / signature_perfumes / items / properties / pyramid / additionalProperties
```
Removed value: -false
```

AddedOct 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds a genuine behavioral trait not in the annotations: nickname resolution (YSL, MFK, PDM, Paco Rabanne). Return contents are largely covered by the output schema, so this is a solid but not maximal contribution.

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 ordered purpose, capabilities, then usage/exclusions. The capability list is dense but every clause maps to a real return field, and the routing instructions are front-loaded enough to act on immediately.

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, and annotations cover the safety profile. What remains for an agent to decide correctly — what the tool is, when to use it, and which siblings to route to instead — is fully present.

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% and each parameter (house, locale, response_format) is already documented in the schema with examples and enum meanings. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 states a specific resource (perfume house profile) and enumerates exactly what it returns (country, founded year, style, signature perfumes, link), then names the two siblings it is not (list_houses, get_perfume). An agent can distinguish it from all 14 siblings 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?

It gives concrete trigger phrases ('tell me about Creed', 'what is Amouage known for') and explicit exclusions with the correct alternative for each ('Not for browsing all houses (use list_houses) and not for one perfume (use get_perfume)'). This is textbook when-to-use / when-not-to-use routing.

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.