CraveUp MCP Server

Official

by craveup-oss

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Enable or disable takeout pickup

set_takeout_enabled

Idempotent

Enable or disable takeout for a restaurant location. When enabling, the location's main schedule is applied to takeout settings.

Instructions

Turn takeout on/off for a location. Copies the location main schedule when enabling. 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": "set_takeout_enabled"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Preview by default. Apply requires the exact returned planDigest.	dry-run
`enabled`	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?

Annotations mark this as non-read-only, idempotent, and non-destructive; the description adds that enabling copies the location main schedule and that login is required. This enriches the behavioral profile beyond the annotations without contradicting them. There is no statement that conflicts with the annotation hints.

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 short sentences; the first delivers the core action and the second adds a critical side effect and auth requirement. No wasted words.

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?

With annotations, schema, and an output schema available, the description fills the remaining gaps: the schedule-copy behavior and the login prerequisite. It doesn't describe the apply/confirmation-token flow, but that is fully covered by the schema. Nothing essential for calling the tool correctly is missing.

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 descriptions already cover mode, planDigest, and confirmationToken, leaving 60% of parameters with schema docs. The description doesn't elaborate on locationId or enabled, but their meaning is readily inferable from the schema names and the tool purpose. No additional parameter semantics are provided, so a baseline score is appropriate.

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?

States a specific verb ('Turn takeout on/off') with a clear resource ('for a location'). The name and title align, and the schedule-copy note adds behavioral specificity. Doesn't explicitly compare to sibling tools, but the domain (takeout) is unambiguous.

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?

The description implies the use case: toggling takeout pickup for a location, but doesn't name alternatives like set_scheduled_orders_enabled or open_location_for_orders. It provides a prerequisite (craveup login) and a behavioral caveat (schedule copy on enable), which is useful but stops short of explicit when/when-not guidance.

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