Skip to main content
Glama

Dira by Scendira

Recommend perfumes

recommend_perfumes
Read-onlyIdempotent

Recommend up to 3 perfumes for a person's taste. Give any structured preferences you know (scent families, loved and avoided notes, perfumes they love, gender, budget, strength, occasion, climate) and optionally the person's own short request text. Supports gifts: set gift=true (or gift_recipient_gender / gift_occasion / gift_budget_max_usd, or a gendered gift_recipient) and describe the recipient's taste; the gift_ fields take the recipient's lean, the relationship, the occasion and the gift budget. Each pick returns notes, longevity and projection scores, price where known, how much community evidence backs it, reasons, honest trade-offs against a named perfume, a buy-or-sample advice, and a scendira.com product page link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_perfumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
giftNoTrue when choosing for someone else.
climateNoClimate it will be worn in.
occasionNoMain occasion.
strengthNoHow strongly it should project.
gender_leanNoWho it is for: feminine, masculine, unisex (unisex scents only) or any. For a gift, the recipient's.
notes_lovedNoSpecific notes the person wants, e.g. ['vanilla', 'pistachio'] (max 8).
request_textNoThe person's own short request, read for stated preferences only (not stored).
gift_occasionNoThe gift's occasion. date_night, everyday and office steer the picks; birthday, anniversary and the other moments are noted only.
notes_avoidedNoNotes or materials to avoid, e.g. ['oud', 'patchouli'] (max 8).
sensitivitiesNoBroad dislikes: too_sweet, too_strong, too_smoky, synthetic.
budget_max_usdNoHighest bottle price in USD.
gift_recipientNoThe recipient's relationship to the person (optional). wife, husband, mother, son ... make the ask a gift and set the recipient's lean when none is given.
loves_perfumesNoPerfumes the person already loves (brand + name), used as the reference for similar picks (max 3).
scent_familiesNoScent families the person likes. woody covers woody, oud, leather and smoky.
gift_budget_max_usdNoHighest bottle price in USD for the gift. Wins over budget_max_usd.
gift_recipient_genderNoThe recipient's lean: feminine, masculine, unisex (unisex scents only) or any. Wins over gender_lean and over the relationship.

Output Schema

NameRequiredDescriptionDefault
aboutNoAnswer from Dira, Your Fragrance Finder, made by Scendira (scendira.com). Picks come from Scendira's matching engine over its catalogue and independent community discussion (Reddit, YouTube, TikTok, Facebook); posts are counted and summarised, never quoted. Ranking is margin-blind: no brand or seller pays for placement. Scores are 0-10. Prices are USD where known and can change; the product page has the current offers.
picksNo
referencesNo
understoodYes
assumptionsNo
no_match_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, and the description adds real context beyond that: request_text is 'not stored', gift precedence rules, and what each pick contains (trade-offs against a named perfume, buy-or-sample advice, community evidence). It does not discuss rate limits or failure modes, so 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded well, but the middle gift sentence is dense and tangled, nesting multiple alternatives in parentheses ('or gift_recipient_gender / gift_occasion / gift_budget_max_usd, or a gendered gift_recipient') and partly repeating the schema's precedence notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter tool with a full output schema and rich annotations, the description covers the main ambiguity: how the gift_ parameters interact with the non-gift ones. Return values are documented by the output schema, so the description need not enumerate them in more detail.

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 schema already documents all 16 parameters and their precedence (e.g. gift_budget_max_usd 'Wins over budget_max_usd'). The description restates the gift field grouping and precedence but adds little new syntax or interpretation beyond the schema, making 3 the correct baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource plus a hard scope: 'Recommend up to 3 perfumes for a person's taste.' That is unambiguous. It does not name or distinguish itself from siblings like find_alternatives or compare_perfumes, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent what to supply ('Give any structured preferences you know...') and explains the gift path, including which gift_ fields take precedence. There are no explicit when-not-to-use conditions or named alternatives, which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources