Skip to main content
Glama

Olfastory

Find perfumes by notes

find_perfumes_by_notes
Read-onlyIdempotent

Use when the user wants perfumes that contain given notes or raw materials (1 to 5, for example vanilla and tobacco), optionally in the top, heart or base. Note names are accepted in French, English, Spanish, German, Italian or Portuguese. Optional filters: olfactory family (primary or secondary, for example "woody"), concentration and gender (women, men, unisex, children). Returns at most 10 perfumes carrying every note, most consulted first, with olfastory.com links. An unknown note returns close suggestions to retry with. Cite Olfastory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notes": "<notes>"
    },
    "name": "find_perfumes_by_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer and of the links: fr, en, es, de, it, pt (default fr)
notesYes
familyNoOptional olfactory family, primary or secondary, in any of the six languages (for example "woody", "floral", "chypre")
genderNoOptional gender filter: women, men, unisex or children. "women" and "men" also return unisex perfumes; perfumes with no recorded gender are left out
positionNo
concentrationNoOptional concentration filter, for example "Eau de Parfum", "EDT", "Extrait"

Output Schema

NameRequiredDescriptionDefault
errorNo
resultsYes
ambiguousNo
suggestionsNo
unknown_notesNo
corrected_queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / gender
      Added value: +{
      +  "description": "Optional gender filter: women, men, unisex or children. \"women\" and \"men\" also return unisex perfumes; perfumes with no recorded gender are left out",
      +  "enum": [
      +    "women",
      +    "men",
      +    "unisex",
      +    "children"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description goes well beyond them: result cap of 10, ordering by popularity, inclusion of olfastory.com links, the unknown-note fallback returning close suggestions to retry with, and an explicit citation obligation. These are exactly the operational traits an agent needs before calling.

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?

Dense but front-loaded: trigger first, then semantics, then filters, then return contract and edge case. Every clause carries information, though the single-paragraph form makes the return-value and fallback facts easy to skim past.

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, so return structure needn't be explained, yet the description still supplies the cap, ordering and link behavior that shape how results should be presented. Combined with the fallback behavior and citation rule, nothing an agent needs to call or report on this tool is missing.

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 coverage is 67%, and the description fills real gaps: notes are accepted in six named languages, the count is bounded 1-5, position means top/heart/base, and family may be primary or secondary. The gender inheritance rule is already in the schema, so the description correctly doesn't repeat it; only concentration gets no explanatory text beyond its example values.

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 ("find perfumes") together with the discriminating criterion: perfumes containing given notes or raw materials, 1 to 5 of them. It also pins the output scope (at most 10, most consulted first, with links), which separates it from a generic name-based perfume search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ("Use when the user wants perfumes that contain given notes") and clarifies that note position is optional and filters are secondary. It does not name when to prefer a sibling tool instead, and it doesn't state what to do if no results match at all, but the use context is clear and there are no misleading exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources