Skip to main content
Glama
Sign In

10ML Perfume Finder

by com.10ml
OverviewDiscussionsAdmin

Search 10ML guides

search_guides
Read-onlyIdempotent

Find 10ML's perfume and fragrance guides to read or cite: how-tos (where to spray, finding a signature scent, making perfume last), notes explained, house guides, lists, and alternatives guides that compare famous perfumes with similar ones from other houses. Returns title, type and a link per locale. Use whenever you want a source to cite or a deeper read ('how to layer perfume', 'best oud perfumes', 'Creed Aventus dupes guide'). Not for facts about a perfume (use get_perfume) and not for note definitions (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": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNohow-to, list (rankings/comparisons), alternatives (dupes guides), note (a note explained), house (a house mapped)
limitNoResults per page.
queryNoWhat the guide is about. Examples: "how to make perfume last", "oud", "Creed Aventus dupes", "gift". Omit to browse.
cursorNonext_cursor from the previous page.
localeNoLanguage of the 10ml.com links and labels.en

Output Schema

NameRequiredDescriptionDefault
totalYes
guidesYes
sourceYes
messageNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+]
  2. Changed1 schema field changed
    • 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"
+]
  3. Changed5 schema fields changed
    • 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-20, default 8)."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 / guides / items / properties
      Removed value: -{
-  "title": {
-    "type": "string"
-  },
-  "topics": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "translated": {
-    "type": "boolean"
-  },
-  "type": {
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}
    • removedOutput schema / properties / guides / items / required
      Removed value: -[
-  "title",
-  "type",
-  "topics",
-  "url",
-  "translated"
-]
  4. Changed4 schema fields changed
    • removedOutput schema / properties / guides / items / properties / translated / description
      Removed value: -"False when the guide is only available in English (the url is then the English page)"
    • 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"
  5. Changed6 schema fields changed
    • 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 / guides / items / additionalProperties
      Removed value: -false
  6. Added

TDQS

A4.9/5.0
Behavior5/5

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

While annotations cover safety (readOnlyHint: true), the description adds crucial behavioral context by stating exactly what is returned ('title, type and a link per locale'). This makes the agent fully aware of the expected data structure and intent beyond just knowing the operation is read-only.

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?

Despite its length, the description is highly efficient, with every sentence serving a distinct, valuable purpose: defining scope, providing usage examples, defining boundaries, and detailing output.

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?

Given the tool's complexity, including multiple guide types and locale support, the description is extremely complete. It provides all the necessary context—including sibling tool relationships—to ensure the AI agent chooses this tool accurately.

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?

Although the schema coverage is 100%, the description adds vital semantic meaning to the 'type' and 'query' parameters. Specifically, it clarifies that 'alternatives guides' compares famous perfumes with similar ones, a nuance not explicitly detailed in the enumeration schema.

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 clearly states the purpose is to find 'perfume and fragrance guides to read or cite.' It comprehensively categorizes the content, mentioning how-tos, notes explained, house guides, and alternatives, thereby sharply defining its function.

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?

The usage guidelines are exceptional because they provide direct comparisons and explicit exclusions. It tells the user to use this tool for deep reading/citation and explicitly excludes it for factual lookups (direct use of get_perfume) or note definitions (direct use of explain_note).

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 toolsInspect
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.

Resources