10ML Perfume Finder

Explain a perfume term

explain_perfume_term

Read-onlyIdempotent

Explain perfume vocabulary and fragrance families: concentrations (eau de cologne, eau de toilette, eau de parfum, extrait, elixir), sillage, projection, longevity, dry down, accord, top/heart/base notes, flanker, maceration, layering, niche vs designer, plus the 23 fragrance families (chypre, fougere, gourmand, oriental / amber...) with their key notes and example perfumes. Use for 'what is the difference between EDT and EDP', 'what is a chypre', 'what does sillage mean'. Leave term empty to list everything covered. Not for individual notes (use explain_note).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain_perfume_term"
  }
}

Input Schema

Name	Required	Description	Default
`term`	No	A term or family. Examples: "EDP", "sillage", "chypre", "dry down", "fougere". Omit to list all terms.
`limit`	No	Results per page.
`cursor`	No	next_cursor from the previous page.
`locale`	No	Language of the 10ml.com links and labels.	en

Output Schema

Name	Required	Description	Default
`total`	Yes
`source`	Yes
`matches`	Yes
`message`	No
`available`	No
`next_cursor`	No
`suggestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "ro",
-  "el",
-  "hu",
-  "cs",
-  "pl",
-  "nl"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "ro",
+  "el",
+  "hu",
+  "cs",
+  "pl",
+  "nl",
+  "pt",
+  "sv",
+  "da",
+  "fi",
+  "bg",
+  "hr"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "ro",
-  "el",
-  "hu",
-  "cs",
-  "pl"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "ro",
+  "el",
+  "hu",
+  "cs",
+  "pl",
+  "nl"
+]

Changed5 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-60, default 12)."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 / matches / items / properties

Removed value: -{
-  "definition": {
-    "type": "string"
-  },
-  "example_perfumes": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "key_notes": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "kind": {
-    "enum": [
-      "term",
-      "family"
-    ],
-    "type": "string"
-  },
-  "name": {
-    "type": "string"
-  },
-  "related": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "subfamilies": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / matches / items / required

Removed value: -[
-  "kind",
-  "name",
-  "definition",
-  "related"
-]

Changed4 schema fields changedOct 20, 2026

removedOutput schema / properties / available / description

Removed value: -"Every term and family covered (only when term is omitted)"

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 / total / description
```
Removed value: -"How many results matched in all"
```

Changed6 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 / matches / items / 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 readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description adds genuine context on content coverage (23 families with key notes and example perfumes) and on what an empty term returns. It does not discuss pagination behavior or that results carry 10ml.com links, which the locale parameter hints at but the prose never mentions.

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, then scope, then usage, then the exclusion — a sensible ordering with no filler sentences. The long parenthetical enumerations are useful for matching but make the first sentence heavy.

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?

An output schema exists, safety is covered by annotations, and all parameters are documented in the schema, so the description only needs to convey domain scope and routing — which it does thoroughly, including the empty-term listing path and the note-tool boundary.

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 the schema already documents all four parameters including the term examples and pagination cursor. The description's 'leave term empty to list everything covered' largely restates the schema's 'Omit to list all terms', and it says nothing about limit/cursor paging or the locale's effect on link language.

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?

A specific verb ('Explain perfume vocabulary') paired with an unusually explicit scope: concentrations, performance terms, note structure, market categories, and the 23 fragrance families. It also names the sibling it is not (explain_note), so an agent can separate this from the note-explanation tool without opening either 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 triggering queries ('what is the difference between EDT and EDP', 'what is a chypre', 'what does sillage mean'), states the empty-term behavior, and explicitly excludes individual notes by naming the correct alternative. Both when-to-use and when-not-to-use are stated.

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.