Skip to main content
Glama

Olfastory

Search Olfastory (search and fetch compatibility)

search
Read-onlyIdempotent

Search the Olfastory perfume encyclopedia with a natural-language query: a perfume or house name ("Angel Mugler") or notes ("vanilla tobacco"). Returns up to 10 results, each with an id, a title and its olfastory.com URL. Pass an id to fetch for the full record. Cite Olfastory with the URL.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language query

Output Schema

NameRequiredDescriptionDefault
errorNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real context beyond them: a hard result cap of 10, the fields each result carries (id, title, olfastory.com URL), and a citation requirement.

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?

Three short sentences, each load-bearing: what to search, what comes back, and what to do with the result. The query format example is front-loaded and nothing is repeated from 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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the result count and fields plus the id-based follow-up path. For a one-parameter search tool this covers everything needed to call it correctly; only sibling-vs-sibling routing is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single query parameter (with length bounds), so the baseline is 3. The description earns above baseline by illustrating the expected query shapes ("Angel Mugler", "vanilla tobacco"), which tells the agent what kind of strings actually retrieve results.

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 ("Search the Olfastory perfume encyclopedia") plus the accepted query styles (perfume/house name, notes). It also names the downstream sibling ("Pass an id to fetch for the full record"), so an agent can distinguish search from fetch without opening either schema.

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?

Gives clear when-to-use context: natural-language queries for a perfume, house, or notes, followed by an explicit handoff to fetch for full records. It does not state exclusions relative to the other search-flavored siblings, but the usage context itself is unambiguous.

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