CraveUp MCP Server

Official

by craveup-oss

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Update location store hours

update_store_hours

Idempotent

Set when a location accepts orders by applying a 24/7, business-hours, or custom weekly schedule, with dry-run preview before applying.

Instructions

Set when a location accepts orders. Use preset always_open for dev/demo, or pass a custom 7-day schedule. Requires craveup login.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_store_hours"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Preview by default. Apply requires the exact returned planDigest.	dry-run
`scope`	No	organization updates the shared default; location creates or updates this location override	location
`preset`	No	always_open = 24/7; business_9am_10pm; custom = provide schedule	always_open
`schedule`	No
`locationId`	No
`planDigest`	No	Exact digest returned by a dry-run of the same arguments.
`confirmationToken`	No	Required exact phrase for destructive, paid, or release operations.

Output Schema

Name	Required	Description	Default
`data`	No
`mode`	Yes
`status`	Yes
`changes`	Yes
`summary`	Yes
`operation`	Yes
`planDigest`	Yes
`environment`	Yes
`nextActions`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Aug 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish a mutating but non-destructive and idempotent operation, so the description only needs to add behavioral context. It contributes the authentication requirement via 'Requires craveup login.' It does not contradict any annotation, and 'Set when a location accepts orders' consistently implies a write operation.

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 two short sentences with the core action front-loaded and no filler. Every sentence earns its place: one states what the tool does and the other gives preset and authentication context.

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

Completeness4/5

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

The input schema is unusually detailed and an output schema exists, so the description can focus on high-level context. It supplies the login requirement and the 7-day custom schedule, but for a 7-parameter workflow it could also mention the dry-run/apply model at the tool level; nevertheless, the schema covers that gap.

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?

The description adds some parameter-level meaning by explaining that always_open is for dev/demo and that a custom preset requires a 7-day schedule. The input schema already provides substantial descriptions for mode, scope, planDigest, and confirmationToken, so the description does not need to repeat those.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the active verb 'Set' and defines the resource as 'when a location accepts orders,' which clearly identifies the operation as updating recurring store hours. It does not explicitly distinguish itself from sibling tools like open_location_for_orders or set_scheduled_orders_enabled, but the mention of presets and a weekly schedule conveys the recurring-hours semantics.

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?

It gives conditional usage guidance: 'Use preset always_open for dev/demo, or pass a custom 7-day schedule,' and it notes the cravingup login prerequisite. However, it does not say when to prefer this tool over the many sibling location and schedule tools, nor does it offer exclusions or alternatives.

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