Skip to main content
Glama
slavins-co

CellarTracker MCP

by slavins-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recent-deliveries

Read-only

List wines received in a date range by delivery date, defaulting to the past 30 days. Use it to track what just landed in your cellar.

Instructions

List wines actually delivered (received) in a date range, keyed on DeliveryDate. Defaults to the last 30 days. Use this for 'what just landed', unlike purchase-history which keys on order date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storeNoStore name filter
date_toNoEnd delivery date (YYYY-MM-DD). Defaults to today.
date_fromNoStart delivery date (YYYY-MM-DD). Defaults to 30 days ago.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
totalYes
mostRecentDeliveryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv0.5.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the 30-day default window, but that is also stated in the schema, and it says nothing about result ordering, volume, or pagination behavior for what could be a long list.

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?

Two tightly written sentences with zero waste; the date-range scope and default lead, with the sibling distinction following.

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?

An output schema exists, so return values need no explanation. For a simple filtered read-only list, the description plus schema and annotations give an agent everything needed to call it correctly.

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 all three parameters are already documented with formats and defaults. The description reinforces date-keying semantics but adds no syntax or format detail beyond the schema; 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?

States a specific verb and resource ('List wines actually delivered') and immediately names the keying field (DeliveryDate), which distinguishes it from siblings like purchase-history at a glance.

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?

Explicitly gives the when-to-use ('what just landed') and names the alternative tool plus the discriminating condition (order date vs delivery date). No inference required.

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