Scento Perfume API (MCP server)

Official

by Scento-com

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Search the Scento journal

journal-search

Read-onlyIdempotent

Find Scento journal articles, guides, and background reading on perfumes, houses, notes, or topics like layering, returning titles, summaries, and language-matched scento.com links.

Instructions

Use this when the user wants articles, guides or background reading on a perfume, fragrance, cologne, house, note or topic (for example layering, vetiver, how to make a scent last). Returns matching Scento journal articles with title, one-line summary and scento.com link in the user's language. Use it to give the reader something to read on. Don't use for a perfume's notes (perfume-portrait), a house profile (house-portrait) or a term's meaning (perfumery-lexicon).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	Yes	A perfume, house, note or topic to find articles on. Examples: "vetiver", "layering", "Creed Aventus", "make a scent last".
`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
`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.

Changed3 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 / q / description

Previous value: -"A perfume, house, material or topic, for example “vetiver”, “layering” or “Creed Aventus”."New value: +"A perfume, house, note or topic to find articles on. Examples: \"vetiver\", \"layering\", \"Creed Aventus\", \"make a scent last\"."

First observedv0.1.0Oct 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond them: the exact return payload (title, one-line summary, scento.com link), the localization behavior (links in the user's language, answers in English), and the reader-facing intent. It does not mention pagination, which is the one behavioral gap.

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, front-loaded with the trigger condition, then return shape, then exclusions. Every clause carries load — the examples, the output fields and the sibling routing all serve selection or invocation.

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?

For a 3-parameter read-only search with full schema coverage and an output schema, the description supplies everything an agent needs: trigger, exclusions, sibling routing and localization behavior. Return values are already covered by the output schema, so nothing material 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 the baseline is 3 and the schema already documents q, lang and continuation thoroughly. The description reinforces the localization nuance ('in the user's language') but adds no syntax, format or constraint detail beyond the schema, so it earns no more than baseline.

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 ('search the Scento journal'), names the artifact returned (articles with title, one-line summary and link), and explicitly contrasts itself with three siblings. An agent can distinguish it from perfume-portrait, house-portrait and perfumery-lexicon 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 when-to-use trigger ('user wants articles, guides or background reading on a perfume, fragrance, cologne, house, note or topic') with concrete examples, plus explicit when-not-to-use routing to three named alternatives. 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