Skip to main content
Glama

Dira by Scendira

Compare perfumes

compare_perfumes
Read-onlyIdempotent

Compare 2 to 4 named perfumes side by side: notes, longevity, projection, blind-buy safety, price and community evidence. Optionally pick a winner on chosen criteria, or say which is closer in scent to a third perfume. A winner is named only when every perfume was found and measured on every criterion and one is clearly ahead.

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": {
      "perfumes": "<perfumes>"
    },
    "name": "compare_perfumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
criteriaNoWhat to compare on: longevity, projection, blind_buy_safety, price.
perfumesYesPerfume names (brand + name), 2 to 4.
closer_toNoA third perfume: which candidate smells closer to it.
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.
itemsYes
statusYes
winnerNoSet only when every perfume was found and measured on every criterion and one is clearly ahead.
criteriaNo
referenceNo
assumptionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's real contribution is the winner-determination rule: a winner is named only when every perfume was found and measured on every criterion and one is clearly ahead. That is a substantive disclosure of conditional output behavior an agent could not infer from the annotations. It stops short of saying what the response looks like when a perfume is not found.

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?

Three sentences, front-loaded with the core action and scope, followed by optional modes and then the winner caveat — nothing is redundant. The final sentence is longer than needed but carries the most decision-relevant information, so it earns its place.

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?

With an output schema present and 100% parameter coverage, the description need not explain return values, and it covers the main modes plus the winner-condition. The only real gap is silence on budget_max_usd and on behavior when one of the named perfumes cannot be found, which matters for a tool that explicitly gates its answer on full measurement.

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 parameters are already well documented and the baseline is 3. The description adds mild meaning by explaining that closer_to is 'a third perfume' used for similarity ranking and that criteria drive winner selection, but budget_max_usd is never mentioned and no format or interaction detail goes beyond the schema.

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 ('Compare 2 to 4 named perfumes side by side') and enumerates the compared dimensions (notes, longevity, projection, blind-buy safety, price, community evidence). It clearly distinguishes the operation from recommend/lookup style siblings by framing it as a comparative analysis, though it never names an alternative sibling explicitly.

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?

It implies the two usage modes — ranking a winner on chosen criteria, or ranking by scent similarity via a third perfume — which is useful context. However, it never states when to prefer this over find_alternatives or recommend_perfumes, nor any exclusions, so the routing guidance is only implied.

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