Scento Perfume API (MCP server)

Official

by Scento-com

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Pick perfumes for an occasion

occasion-edit

Read-onlyIdempotent

Pick a perfume for an occasion, season or climate, such as wedding, office, date night, summer or cold weather. Returns a short edit with why each fits and a Scento link.

Instructions

Use this when the user asks which perfume, fragrance or cologne to wear for one occasion, season or climate: wedding, office, date night, night out, weekend, everyday, gym or sport (workout), summer days, cold weather, first impressions, long-lasting or under-the-radar. Returns a short edit of perfumes with a line on why each fits and a scento.com link for each, in the user's language. The occasion is a fixed list, so pick the nearest value; omit gender_lean unless the user states one. For several occasions call it once per occasion. Don't use for a collection built around perfumes the user already loves (wardrobe-composer) or for similar scents (scent-neighbours).

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
`occasion`	Yes	The occasion, season or climate. Examples: "wedding" for a wedding guest, "office" for work, "weekend" for relaxed days, "gym" for sport, "date-night" for an evening out for two, "summer-days" for heat, "cold-weather" for winter. A summer wedding is "wedding".
`gender_lean`	No	Omit unless the user states one ("cologne" or "perfume" alone is not a request). Lean read from the materials by convention: "feminine", "masculine" or "shared". Example: "masculine" when the user asks for a men's fragrance. It reorders the edit and never excludes a perfume.

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

Previous value: -"Optional lean, read from the materials by convention; it reorders the edit and never excludes a perfume."New value: +"Omit unless the user states one (\"cologne\" or \"perfume\" alone is not a request). Lean read from the materials by convention: \"feminine\", \"masculine\" or \"shared\". Example: \"masculine\" when the user asks for a men's fragrance. It reorders the edit and never excludes a perfume."

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

Previous value: -"The occasion to edit for."New value: +"The occasion, season or climate. Examples: \"wedding\" for a wedding guest, \"office\" for work, \"weekend\" for relaxed days, \"gym\" for sport, \"date-night\" for an evening out for two, \"summer-days\" for heat, \"cold-weather\" for winter. A summer wedding is \"wedding\"."

changedInput schema / properties / occasion / enum

Previous value: -[
-  "office",
-  "date-night",
-  "night-out",
-  "everyday",
-  "summer-days",
-  "cold-weather",
-  "workout",
-  "first-impressions",
-  "long-lasting",
-  "under-the-radar"
-]New value: +[
+  "office",
+  "date-night",
+  "night-out",
+  "everyday",
+  "summer-days",
+  "cold-weather",
+  "workout",
+  "wedding",
+  "weekend",
+  "first-impressions",
+  "long-lasting",
+  "under-the-radar",
+  "gym",
+  "sport"
+]

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 readOnlyIdempotent non-destructive behavior, so the safety profile is covered. The description still adds behavioral context beyond them: the response is a 'short edit' with a per-perfume rationale and a scento.com link, links follow the user's language while answers stay English, and the occasion input is a closed list requiring nearest-value snapping. The return-shape detail overlaps the existing output schema, which keeps this 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?

Front-loaded with the trigger, then constraints, then exclusions, so an agent can stop reading early. It is dense rather than bloated, though the long inline enumeration of occasions partly duplicates the enum values already in the schema.

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?

Purpose, trigger, parameter resolution, multi-call behavior, output shape, and sibling routing are all present for a 3-param read-only tool with an output schema. An agent has everything needed to select and invoke it correctly, including the gender_lean omission default.

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% and the schema already documents all three parameters with enums, defaults and examples. The description only adds the closed-list resolution rule ('pick the nearest value') and 'omit gender_lean unless the user states one', both of which largely restate the schema. Baseline 3 is right when the schema does the heavy lifting.

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 (pick perfumes for an occasion) and enumerates the exact occasion space it covers. It explicitly names two siblings it is NOT (wardrobe-composer, scent-neighbours), so an agent can route between them 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 trigger conditions ('when the user asks which perfume... to wear for one occasion, season or climate'), exclusion conditions (wardrobe-composer for a collection built around loved perfumes, scent-neighbours for similar scents), and a multi-call rule ('for several occasions call it once per occasion'). Nothing about when to use it 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