Skip to main content
Glama

Dira by Scendira

Look up a perfume

lookup_perfume
Read-onlyIdempotent

Look up one perfume by name: concentration, scent family, notes pyramid, main accords, a one-line scent description, longevity, projection and blind-buy safety scores, price where known, community evidence and its scendira.com page. Returns close catalogue matches when the name is not found.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBrand and name, e.g. 'Kayali Vanilla 28'.

Output Schema

NameRequiredDescriptionDefault
noteNo
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.
foundYes
perfumeNo
did_you_meanNo

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond them: the full set of attributes returned and the fuzzy fallback that returns close catalogue matches when the name is not found. Return-format and pagination detail are absent but partially covered by the output schema.

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?

The core action and scope are front-loaded in the first clause, and the fallback case trails correctly. The mid-sentence attribute list is long but each item tells the agent what it can retrieve, so it earns its space; only the price hedge ("where known") could be tightened.

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 one-parameter read-only lookup with an output schema, the description covers what the tool is, what it returns at a high level, and how it degrades on a miss. The only gap is guidance on when a caller should prefer the sibling comparison/recommendation tools instead.

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?

With a single parameter at 100% schema coverage, the schema already carries the meaning, including the 'Brand and name' format and an example. The description adds only the fuzzy-match semantics for inexact names, which is useful but marginal; baseline for a fully documented single parameter is a 3.

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: "Look up one perfume by name," and enumerates exactly what the lookup yields (notes pyramid, accords, scores, price, page). The scoping word "one" distinguishes it from the comparison/alternative siblings, though no sibling is named explicitly, which keeps it just below 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 Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it should call this when it already has a specific perfume name. There is no explicit when-to-use or when-not-to-use guidance relative to compare_perfumes, find_alternatives, or recommend_perfumes. The fallback note about close catalogue matches gives partial behavioral routing but not selection criteria.

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