Scento Perfume API (MCP server)

Official

by Scento-com

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Find similar perfumes

scent-neighbours

Read-onlyIdempotent

Find perfumes similar to a given scent by shared notes and structure, with differences explained and scento.com links in your language.

Instructions

Use this when the user asks for perfumes similar to, like or in the same style as a given perfume, fragrance or cologne, or what else to try if they love it (synonyms: similar to, smells like, more like, if I like X). Returns the perfumes that share the most notes and structure with it, with the shared materials named, one line on how each differs and scento.com links in the user's language. Don't use for one perfume's own notes (perfume-portrait), a side-by-side of named perfumes (perfume-contrast) or a whole collection (wardrobe-composer).

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	The perfume the user already knows or loves, by name (with its house if needed) or slug. Examples: "Aventus", "Layton Parfums de Marly", "Santal 33".
`same_house`	No	Set true to stay within the perfume's own house, for example when asked for "other Creed scents like Aventus". Default false.
`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 / perfume / description

Previous value: -"The perfume to start from, by name (with its house if needed) or slug."New value: +"The perfume the user already knows or loves, by name (with its house if needed) or slug. Examples: \"Aventus\", \"Layton Parfums de Marly\", \"Santal 33\"."

changedInput schema / properties / same_house / description

Previous value: -"Only look within the same house."New value: +"Set true to stay within the perfume's own house, for example when asked for \"other Creed scents like Aventus\". Default false."

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 declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: results share the most notes and structure, shared materials are named, each entry gets a one-line difference note, and links come back in the user's language. It does not cover pagination/continuation behavior, keeping it short of 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?

Two sentences, front-loaded with the trigger and closed with the exclusions, so the routing information appears before the exclusions. The synonym parenthetical and the three named alternatives make it dense, but each clause carries routing value rather than 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?

With an output schema present and annotations covering the safety profile, the description only needs to add routing and intent, which it does fully: trigger phrases, return semantics, and explicit exclusions naming three siblings. Nothing an agent needs to select or call this tool 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 coverage is 100%, so all four parameters are already documented in the schema, including the lang enum and the perfume examples. The description's mention of

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+resource (find perfumes similar to a given one) with the

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?

Explicit when-to-use with synonyms (

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

Deploy Server