Perfume Picks

search_fragrances

Read-onlyIdempotent

Full-text search across 10,000+ fragrances in the Perfume Picks database. Filter by brand, fragrance family, gender, and MSRP (USD). Returns note pyramids, accords, and community wear scores with source attribution.

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": "search_fragrances"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Brand name filter, e.g. 'Dior'
`limit`	No	Max results (default 10, max 10)
`query`	No	Free-text search: fragrance or brand name
`gender`	No	Marketed gender category of the fragrance; omit to include all
`price_max`	No	Maximum MSRP in USD
`price_min`	No	Minimum MSRP in USD
`fragrance_family`	No	Family filter, e.g. 'woody', 'amber', 'fresh'

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 16, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Max results (default 10)"New value: +"Max results (default 10, max 10)"
```
- changedInput schema / properties / limit / maximum
```
Previous value: -25New value: +10
```
Changed3 schema fields changedAug 31, 2026
- addedInput schema / properties / brand / maxLength
```
Added value: +200
```
- addedInput schema / properties / fragrance_family / maxLength
```
Added value: +120
```
- addedInput schema / properties / query / maxLength
```
Added value: +120
```
First observedAug 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the return payload (note pyramids, accords, community wear scores with source attribution) and states that MSRP is USD, which nothing in the structured fields supplies.

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 catalog scope, followed by filters and return content. No filler, no repetition of the schema.

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 no output schema, the description usefully covers return contents, and annotations cover safety, so an agent can call it informed. Minor gaps remain — no ranking/relevance behavior and no mention of the hard 10-result cap's effect on result interpretation.

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 seven parameters are already documented in the schema, and the description only restates the filter set (brand, family, gender, MSRP). Baseline 3 is appropriate; no format or matching-behavior detail is added.

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 ("Full-text search across 10,000+ fragrances") plus the catalog scope, so the agent knows exactly what it retrieves. It does not, however, contrast itself against near-neighbors like find_similar or get_fragrance, whose purposes overlap at a glance.

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

Usage Guidelines2/5

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

The description lists available filters but gives no when-to-use guidance and names no alternatives, despite several siblings (find_similar, find_dupes, get_recommendations, trending_fragrances) that could plausibly be chosen instead. The agent has to infer that this is the keyword-search entry point.

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

All Perfume Picks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.