Skip to main content
Glama
mame0001

sakenowa-mcp

by mame0001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SAKENOWA_CACHE_DIRNowhere the JSON snapshot is cached~/.cache/sakenowa-mcp
SAKENOWA_TTL_SECONDSNohow long before the cache auto-refreshes (in seconds)604800

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
sync_sakenowa_dataA

Fetch/refresh the Sakenowa open dataset into a local cache and report its scale. The cache auto-refreshes weekly, so you rarely need this — call it with force=True only to pull the latest monthly snapshot immediately.

Returns dataset counts, the data's year-month, and the required attribution.

search_sakeA

Find sake by brand name or brewery name and return their IDs.

Names are Japanese; kanji queries (e.g. 八海山, 獺祭) match directly, and
so do Chinese kanji that share the glyphs. Use `area` to filter by
prefecture name (e.g. '新潟'). Use the returned `id` with
get_sake_profile / find_similar_sake / compare_sake.
get_sake_profileA

Return the six-axis flavor profile of one sake: an ASCII radar, the dominant flavor tags, an estimated four-type class (薫/爽/醇/熟, heuristic), and its overall/area popularity rank.

Also lists the bottle-spec fields the Sakenowa dataset does NOT provide
(polishing ratio, SMV, ABV, price, …) so they are never invented.
find_similar_sakeA

★ Core feature ★ Given one sake, find others by flavor-vector proximity.

`mode` steers the direction in flavor space:
  - similar       : nearest overall (a true taste-alike)
  - drier         : like this, but drier
  - sweeter       : like this, but less dry / rounder
  - lighter       : like this, but lighter & crisper
  - richer        : like this, but fuller & heavier
  - more_aromatic : like this, but more floral/fragrant
  - calmer        : like this, but quieter on the nose
  - contrast      : the opposite palate (for deliberate exploration)

Only sake that have a flavor chart can be matched.
compare_sakeA

Compare 2–5 sake side by side across all six flavor axes, with the spread (max−min) per axis to highlight where they differ most.

Prompts

Interactive templates invoked by user choice

NameDescription
recommend_sakeRecommend Japanese sake matching a described taste or mood.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: searching, profiling, comparing, finding similar, and data sync. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., search_sake, get_sake_profile), making them predictable.

Tool Count5/5

Five tools is well-scoped for a domain-specific sake exploration server. It covers core functionality without being overwhelming or too sparse.

Completeness4/5

The tool set covers the main workflow: search, get profile, compare, and find similar. Minor gaps like lack of filtering by flavor attributes or listing all sake, but overall adequate.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources