Israel Grocery MCP

Overview Schema Source Related Servers Discussions Admin

set_preferences

Set your grocery shopping preferences for Shufersal and Tiv Taam to guide price comparisons and cart automation based on store, strategy, organic, budget, and brand choices.

Instructions

Set your shopping preferences.

Args:
    preferred_store: Default store ("shufersal" or "tivtaam"). None = always compare.
    shopping_strategy: "cheapest" | "preferred_store" | "quality"
    prefer_organic: Prefer organic products when available.
    prefer_budget: Prefer sale/discounted products.
    prefer_store_brand: Prefer Shufersal-brand products.
    preferred_brands: Brand names to prefer (e.g. ["Tnuva", "Osem"]).
    banned_keywords: Words to avoid in product names.
    skip_pantry: Skip common pantry staples (salt, oil, spices) when parsing recipes.
    tivtaam_branch_id: Override Tiv Taam branch ID (default: 943).

Input Schema

TableJSON Schema

Name	Required	Default
`skip_pantry`	No
`prefer_budget`	No
`prefer_organic`	No
`banned_keywords`	No
`preferred_store`	No
`preferred_brands`	No
`shopping_strategy`	No	cheapest
`tivtaam_branch_id`	No
`prefer_store_brand`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It says nothing about persistence (are preferences saved across sessions?), authentication requirements (does it need login?), side effects, or reversibility. For a configuration tool that likely alters how other tools behave, this is a meaningful gap.

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?

The description is compact and front-loads the one-sentence summary before listing parameters. It avoids filler. The parameter list is dense but readable, though it could be slightly better organized with consistent punctuation or grouping.

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

Completeness3/5

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

There is an output schema, so return values need not be explained. The description covers all 9 parameters with minimal context, but it lacks usage guidance and behavioral details that are important for a preferences-setting tool with no annotations. It is minimally adequate but has clear gaps.

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 description coverage is 0%, so the description's parameter explanations are the only source of meaning. It clarifies ambiguous parameters like shopping_strategy with enum values, preferred_store with allowed values, and gives examples for preferred_brands. However, not all parameters are fully explained (e.g., tivtaam_branch_id default is stated but purpose is vague), and the prose is somewhat cramped rather than thorough.

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 opens with 'Set your shopping preferences', a specific verb+resource that clearly distinguishes this configuration tool from sibling actions like login, search, or cart operations. There is no ambiguity about what the tool does.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It doesn't state whether preferences are persisted, whether they affect all subsequent sessions, or whether to call it before or after other tools. The agent must infer that setting preferences is a prerequisite for personalized shopping from the sibling tool names alone.

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

Deploy Server