Fragrance & Perfume MCP (Noteboxd)

user_taste_compare

Read-onlyIdempotent

Compare your taste with another user — compatibility score, shared and divergent notes/accords/families, and an optional AI overview. Free for any signed-in account; the AI overview needs Pro and is left out otherwise.

See also: user_taste_public for a user's top preferences · user_taste_summary for your own summary.

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": {
      "target_user_id": "<target_user_id>",
      "context": "<context>"
    },
    "name": "user_taste_compare"
  }
}

Input Schema

Name	Required	Description	Default
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`with_overview`	No	Include the AI overview (Pro only; left out for free accounts)
`target_user_id`	Yes	User ID to compare your taste with
`response_format`	No		markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / with_overview / description

Previous value: -"Include AI-generated overview (requires Pro)"New value: +"Include the AI overview (Pro only; left out for free accounts)"

Changed2 schema fields changedOct 27, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "target_user_id"
-]New value: +[
+  "target_user_id",
+  "context"
+]

Changed3 schema fields changedOct 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "target_user_id",
-  "context"
-]New value: +[
+  "target_user_id"
+]

First observedOct 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the added value here is the auth and entitlement detail: free for any signed-in account, with the AI overview requiring Pro and being silently omitted otherwise. That omission behavior is genuinely useful context an agent cannot get from annotations. It does not cover failure modes for an unknown or private target_user_id.

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?

The core capability and its output surface are front-loaded in the first sentence, with entitlement caveats and sibling routing following in priority order. No sentence is redundant with the schema or annotations.

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?

There is no output schema, and the description compensates by naming the returned components (compatibility score, shared/divergent facets, optional AI overview). Combined with the entitlement note, an agent has enough to call it correctly. Edge behavior for invalid, private, or self-referencing target users is the remaining gap.

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 coverage is 75%, with the heavy 'context' parameter heavily documented and 'with_overview' explained inline, so the schema does most of the work. The description adds only that the overview is optional and Pro-gated, and that comparison is against 'another user'. response_format carries no description in either place, but the enum is self-explanatory.

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

Purpose5/5

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

States a specific verb and resource ('Compare your taste with another user') and enumerates the outputs: compatibility score, shared/divergent notes/accords/families, optional AI overview. The trailing 'See also' line explicitly separates it from user_taste_public and user_taste_summary, so an agent can route without opening schemas.

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?

The 'See also' line names both adjacent tools and what each does, which implies the selection rule: this tool for two-user comparison, the others for single-user views. It also gives entitlement guidance (free for signed-in accounts, Pro for the AI overview). It stops short of explicit when-not-to-use conditions such as private or invalid target users.

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

All Fragrance & Perfume MCP (Noteboxd) 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.