Skip to main content
Glama

Olfastory

Fetch an Olfastory record (search and fetch compatibility)

fetch
Read-onlyIdempotent

Fetch the full Olfastory record of a perfume by an id returned by search (or an olfastory.com URL): house, year, concentration, perfumers, olfactory family, notes pyramid and a one-sentence presentation, with its URL. 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id returned by search, or an olfastory.com URL

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
textNo
errorNo
titleNo
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot: the exact shape of what comes back and an attribution obligation ('Cite Olfastory with the URL'), which is a real output-side requirement an agent must honor.

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?

One dense but front-loaded sentence: the verb and resource lead, the returned fields follow, and the citation rule closes it. No filler, though the enumerated field list plus parenthetical makes it a single long clause chain rather than cleanly segmented guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only lookup with rich annotations and an output schema, the description supplies everything needed: where the id comes from, what the record contains, and the citation duty. Return-value detail is correctly left to the output schema.

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% and the single parameter's description already says 'An id returned by search, or an olfastory.com URL'. The description restates the same accepted input forms without adding syntax, normalization or error behavior beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource (fetch the full Olfastory record of a perfume) and enumerates the payload: house, year, concentration, perfumers, olfactory family, notes pyramid, presentation, URL. It also states the input's origin (an id returned by search or an olfastory.com URL), so an agent can tell this is the detail-expansion step that follows a search call.

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 usage context: call it with an id produced by search, or with an olfastory.com URL. It does not state exclusions or when a different lookup tool would be preferable, but the triggering condition 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