Scento Perfume API (MCP server)

Official

by Scento-com

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Find perfumes by note

material-match

Read-onlyIdempotent

Find perfumes that contain specific notes or raw materials, optionally in the top, heart, or base, and see each match's house and pyramid placement.

Instructions

Use this when the user wants perfumes, fragrances or colognes that contain specific notes or raw materials, optionally in the top, heart or base (synonyms: with notes of, built on, smells of, containing; for example vanilla and tobacco in the base). Returns the perfumes that have every material given, with house, where each sits in the pyramid and scento.com links in the user's language. Don't use to explain one material (note-portrait), to find perfumes like a named perfume (scent-neighbours) or for a mood or occasion (occasion-edit).

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
`tier`	No	Where in the pyramid the materials must sit: "top", "heart" or "base". Example: "base" for a vanilla-and-tobacco drydown. Default "any".	any
`family`	No	Optional Scento family to stay within, for example “Wood & Root”.
`materials`	Yes	One to four notes or raw materials that must all be present. Examples: ["vanilla", "tobacco"] or ["oud"].
`continuation`	No	The "continuation" value from a previous answer, passed back unchanged to get the next part of the list.

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.

Changed4 schema fields changedv0.1.1Oct 21, 2026

changedInput schema / properties / continuation / description

Previous value: -"From a previous answer, for the next part of the list."New value: +"The \"continuation\" value from a previous answer, passed back unchanged to get the next part of the list."

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 / materials / description

Previous value: -"One to four notes or raw materials that must all be present."New value: +"One to four notes or raw materials that must all be present. Examples: [\"vanilla\", \"tobacco\"] or [\"oud\"]."

changedInput schema / properties / tier / description

Previous value: -"Where in the pyramid the materials must sit."New value: +"Where in the pyramid the materials must sit: \"top\", \"heart\" or \"base\". Example: \"base\" for a vanilla-and-tobacco drydown. Default \"any\"."

First observedv0.1.0Oct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive safety, so the bar is lower. The description adds real behavioral detail beyond that: results must contain EVERY material given (conjunction, not union), the payoff fields (house, pyramid position, scento.com links), and that labels/links localize while answers stay English. It stops short of disclosing result count or pagination behavior, hence not a 5.

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, then output, then exclusions — a sensible ordering. The synonym parenthetical is dense but earns its place by catching varied user phrasing. Slightly long overall, but no sentence is wasted.

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?

With an output schema present, return values need not be re-explained. The description covers trigger, semantics, localization, alternatives and the continuation mechanism, leaving nothing an agent needs in order to call this correctly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents lang, tier, family, materials and continuation. The description nonetheless reinforces the AND semantics of the materials array, pairs it with a concrete tier example ('vanilla and tobacco in the base'), and explains the language split between links and answers, adding usable meaning above the schema text.

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 (find), resource (perfumes/fragrances/colognes) and constraint (containing specific notes or raw materials), plus the optional pyramid tiers. It names and distinguishes itself from three siblings (note-portrait, scent-neighbours, occasion-edit), so an agent can route correctly 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 an explicit trigger ('when the user wants perfumes... that contain specific notes'), a list of natural-language synonyms to match, and explicit negative routing to note-portrait, scent-neighbours and occasion-edit. Nothing about when/when-not 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