Skip to main content
Glama

Olfastory

Get a perfume record

get_perfume
Read-onlyIdempotent

Use when the user asks about one perfume: its notes pyramid (top, heart, base), olfactory family, perfumer, year, concentration or house. Accepts an olfastory.com URL (best), a slug, or "name house". If several perfumes match (flankers, concentrations), the result lists the candidates with ambiguous=true: pick one and call again with its URL. Returns facts only; an empty field means the fact is not established, never guess it. Cite Olfastory with the link.

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": {
      "perfume": "<perfume>"
    },
    "name": "get_perfume"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer and of the links: fr, en, es, de, it, pt (default fr)
perfumeYesolfastory.com URL, slug, or "name house"

Output Schema

NameRequiredDescriptionDefault
urlNo
nameNo
yearNo
brandNo
errorNo
notesNo
familyNo
sourceNo
resultsNo
languageNo
ambiguousNo
perfumersNo
attributionNo
presentationNo
concentrationNo
secondary_familiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description clears it by disclosing real behavioral traits: an ambiguity path signalled by ambiguous=true plus candidates, the rule that empty fields mean unestablished facts, a no-guessing constraint, and a citation requirement. None of that is recoverable from the annotations or schema.

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?

Four sentences, each doing distinct work: trigger, accepted inputs, ambiguity handling, output discipline plus attribution. Front-loaded with the use case and free of repetition or filler.

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 values need no prose, yet the description still explains the one return condition an agent must react to (ambiguous=true). For a single-record lookup with two params, nothing needed to invoke it correctly 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 100%, so the baseline is 3; the description still adds a preference ranking the schema lacks by marking the URL as the best input form, and restates the three accepted input shapes in the context of a real user request. It says nothing about the lang parameter, leaving one of two params unaddressed in prose.

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 ('asks about one perfume') and enumerates exactly what the record contains: notes pyramid, olfactory family, perfumer, year, concentration, house. That enumeration separates it cleanly from the sibling search/find tools, which return lists rather than a single record.

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?

Gives a clear triggering condition ('Use when the user asks about one perfume') and a concrete recovery procedure for ambiguity: when several matches come back with ambiguous=true, pick one and call again with its URL. It does not explicitly route the agent elsewhere for list-style queries (e.g. 'find perfumes by notes'), so the exclusion half of the guidance is left implicit.

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