Skip to main content
Glama

Dira by Scendira

Find alternatives to a perfume

find_alternatives
Read-onlyIdempotent

Find up to 3 perfumes that smell similar to a named perfume: alternatives, dupes, 'smells like' picks, optionally cheaper than it or within a budget. Uses Scendira's reviewed similarity links and community 'smells like' evidence where they exist, and returns trade-offs against the original (longevity, projection, price).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "perfume": "<perfume>"
    },
    "name": "find_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheaperNoOnly alternatives priced below the named perfume.
perfumeYesBrand and name, e.g. 'Lattafa Khamrah'.
gender_leanNoWho it is for: feminine, masculine, unisex (unisex scents only) or any. For a gift, the recipient's.
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.

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.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so the safety profile is covered; the description adds real value beyond that by disclosing the result cap (max 3), the evidence sources (reviewed similarity links plus community 'smells like'), and what each result carries (trade-offs on longevity, projection, price). It stops short of describing behavior when no similar perfume exists.

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?

Two sentences, front-loaded with the core action and cap, then the evidence and output contract. The synonym list is functional for query matching, and no sentence is slack or repetitive.

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?

An output schema exists so return values need not be spelled out, yet the description still summarizes the trade-off payload. Six parameters are fully documented in schema, the read-only nature is covered by annotations, and an agent has everything needed to invoke this correctly.

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 all six parameters already carry their own definitions including examples and units. The description only re-touches the cheaper and budget filters in prose and adds nothing about how 'smell similar' is computed against notes_avoided or sensitivities; baseline 3 applies.

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?

States a specific verb and resource with hard scope: 'Find up to 3 perfumes that smell similar to a named perfume', and enumerates the query intents it serves (alternatives, dupes, 'smells like'). It is clearly a similarity-search tool rather than a lookup or comparison, but it never names a sibling (e.g. recommend_perfumes) to reinforce the boundary.

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

Usage Guidelines3/5

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

Usage context is implied by the qualifiers ('optionally cheaper than it or within a budget') and by 'where they exist', which hints at evidence fallback, but there is no explicit when-to-use versus when-not guidance or named alternative tool for cases outside the similarity scope.

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