Scento Perfume API (MCP server)

Official

by Scento-com

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get a perfume's notes and profile

perfume-portrait

Read-onlyIdempotent

Look up what a perfume smells like: verified note pyramid, scent family, perfumer, year, concentration, seasons and signature materials from one name or house.

Instructions

Use this when the user asks what a specific perfume, fragrance or cologne smells like, what its notes or pyramid (top, heart, base) are, its family, perfumer, year or concentration (eau de parfum, eau de toilette), or when to wear it (synonyms: notes of, what's in it, how does it smell). Returns the verified note pyramid, Scento family and subfamily, character, seasons and hours, signature materials and the scento.com page in the user's language. Don't use to find similar perfumes (use scent-neighbours), compare perfumes (perfume-contrast) or search by mood (perfume-search).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language of the scento.com links and labels; answers stay in English. Use the language the user writes in, for example "de" (German), "fr" (French), "es" (Spanish) or "it" (Italian). Default "en".	en
`perfume`	Yes	One perfume, by name as the user writes it, optionally with its house, or its slug. Examples: "Oud Wood", "Tom Ford Oud Wood", "Creed Aventus", "santal-33-le-labo".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cite`	Yes
`lede`	Yes
`folio`	Yes
`detail`	Yes
`scento_page`	Yes
`continuation`	Yes
`further_reading`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Oct 21, 2026

changedInput schema / properties / lang / description

Previous value: -"Language of the scento.com links (answers stay in English)."New value: +"Language of the scento.com links and labels; answers stay in English. Use the language the user writes in, for example \"de\" (German), \"fr\" (French), \"es\" (Spanish) or \"it\" (Italian). Default \"en\"."

changedInput schema / properties / perfume / description

Previous value: -"Perfume name, optionally with its house (for example “Oud Wood” or “Tom Ford Oud Wood”), or its slug."New value: +"One perfume, by name as the user writes it, optionally with its house, or its slug. Examples: \"Oud Wood\", \"Tom Ford Oud Wood\", \"Creed Aventus\", \"santal-33-le-labo\"."

First observedv0.1.0Oct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds useful behavior: it discloses that answers stay in English while the scento.com page and labels follow the lang parameter, and that notes are "verified" — context an agent cannot get from the annotations alone. It stops short of describing pagination or failure behavior when the perfume is ambiguous.

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 trigger condition, then returns, then exclusions — a sensible ordering. The middle clause is a long enumeration of attributes and synonyms that borders on padding, but each item maps to a real user asking pattern rather than repeating structured fields.

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 an output schema exists, the description need not explain return shapes, yet it still summarises them usefully. Trigger, localization behavior, and sibling disambiguation are all present; nothing an agent needs to call this correctly is missing.

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 both parameters are fully documented in the schema itself, making 3 the baseline. The description confirms the lang effect ("page in the user's language") and the free-form name-or-slug input, but adds no syntax, disambiguation or matching-behavior detail beyond what the schema already states.

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 (retrieve a perfume's notes and profile) and enumerates the exact attributes covered: notes/pyramid, family, perfumer, year, concentration, occasion. It explicitly names the three siblings it is not and the condition distinguishing each, so an agent can route 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?

Gives explicit when-to-use triggers phrased as user utterances ("what does X smell like", synonym list) and explicit when-not-to-use cases mapped to named alternatives: scent-neighbours for similar, perfume-contrast for comparison, perfume-search for mood. Nothing is left to inference.

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

Deploy Server