Skip to main content
Glama
Sign In
CellarTracker MCP

CellarTracker MCP

by slavins-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drinking-recommendations

Read-only

Sort CellarTracker wines by drinking-window urgency to decide which bottles to open now, next, or hold. Filter by color or occasion.

Instructions

Get wine drinking recommendations sorted by urgency. Orders wines by their listed drinking window: past the window first, then in the final year, then the rest of the window (earliest end first), then not yet open. Status describes the listed window only; CellarTracker's drinkability index (a bottle-count pacing number, not a maturity measure) is reported separately and only breaks ties. Optionally filter by color.

Input Schema

NameRequiredDescriptionDefault
colorNoFilter by color
occasionNoOccasion description
max_resultsNoMaximum results (default 10)

Output Schema

NameRequiredDescriptionDefault
recommendationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.4
    • addedOutput schema / properties / recommendations / items / properties / drinkabilityIndex
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / recommendations / items / properties / windowBegin
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / recommendations / items / properties / windowEnd
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / recommendations / items / properties / windowSource
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / recommendations / items / required
      Previous value: -[
-  "iWine",
-  "wine",
-  "vintage",
-  "status",
-  "window"
-]New value: +[
+  "iWine",
+  "wine",
+  "vintage",
+  "status",
+  "window",
+  "drinkabilityIndex",
+  "windowBegin",
+  "windowEnd",
+  "windowSource"
+]
  2. Changed2 schema fields changedv0.5.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description carries the behavioral load and does it well: it explains the exact sort precedence, clarifies that Status reflects only the listed window, and warns that CellarTracker's drinkability index is a pacing number rather than a maturity measure that only breaks ties. It stops short of covering auth, empty-result, or error behavior.

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?

Three sentences, front-loaded with purpose and ranking rules, and every sentence carries information. The middle sentence is dense with ranking jargon but is not wasteful.

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?

With an output schema present, the description need not explain return fields, and it supplies the one thing an agent could not infer: how results are ordered and how to interpret the status versus the drinkability index. Nothing essential is missing for correct invocation.

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 the schema already documents color, occasion, and max_results. The description only echoes the optional color filter and adds no format, vocabulary, or default details beyond what the schema provides.

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?

The description names a specific verb and resource ('Get wine drinking recommendations') and immediately defines the ordering semantics, which lets an agent distinguish it from siblings like search-cellar or consumption-history.

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

Usage Guidelines3/5

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

Usage is implied by the tool name and the mention of an optional color filter, but there is no explicit statement of when to prefer this over alternatives (e.g. search-cellar) or when not to use it.

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

Deploy Server

Other Tools