Skip to main content
Glama
slavins-co

CellarTracker MCP

by slavins-co

bottle-details

Read-only

Look up individual bottles from your cellar by wine name, barcode, location, bin, or size. Filter by cellar or consumed state, with support for barcode scanning from photos.

Instructions

Look up individual bottles from the Bottles table — the per-bottle view spanning both in-cellar and consumed bottles, with barcode, exact location/bin, and size. Filter by wine name, location, bin, size, or barcode; set state to 'cellar' (default 'all' includes consumed). If the user attaches a photo of a bottle or its barcode, read the barcode digits from the image and pass them as the barcode filter. Location and Bin are account-specific labels, not physical descriptions — if a location/bin filter finds nothing, use cellar-stats with group_by=location or group_by=bin to see the actual values in use. Returns up to max_results per page (default 25) — pass offset to page through more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
binNoSpecific bin/position (e.g. 'Drawer 2', '1-3')
sizeNoBottle format (e.g. '750ml', '1500ml')
queryNoWine name search term
stateNoWhich bottles: 'cellar', 'consumed', or 'all' (default)
offsetNoResult offset for pagination (default 0)
barcodeNoBottle barcode — e.g. read from a photo
locationNoStorage location (e.g. 'Wine Fridge')
max_resultsNoMaximum results (default 25)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
totalYes
offsetYes
bottlesYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral details: pagination (max_results, offset), account-specific labels, and default state. This adds value beyond annotations.

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 description is well-structured: first sentence summarizes purpose, then details filtering, usage tips, and pagination. Every sentence adds value without redundancy.

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?

Given the tool has 8 optional parameters and an output schema, the description covers filters, pagination, error handling (fallback to cellar-stats), and photo-reading hint. No gaps for intended use.

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 descriptions cover all 8 parameters (100%). The description adds context: barcode should be read from photo, location/bin are account-specific, state defaults to 'all' if not specified. It also explains pagination parameters.

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 clearly states it looks up individual bottles from the Bottles table, covering in-cellar and consumed bottles with specific attributes like barcode, location/bin, and size. It distinguishes itself from sibling tools like 'search-cellar' or 'cellar-stats' by focusing on a per-bottle view with detailed filters.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: when a user needs a per-bottle lookup with specific filters. It also tells what to do if filters find nothing (use cellar-stats with group_by) and how to handle barcode input from photos.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/slavins-co/cellartracker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server