Skip to main content
Glama
andhikapraa

Warteg Online MCP Server

by andhikapraa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WARLON_PASSWORDYesYour Warteg Online account password
WARLON_USERNAMEYesYour Warteg Online account username

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginB
    Authenticate with the Warteg Online platform.

    Args:
        username: Your Warteg Online username
        password: Your Warteg Online password

    Returns:
        Success or failure message
get_package_ordersB
    Get all package orders for the authenticated user.

    Returns:
        List of package orders with their IDs and names
get_order_detailsB
    Get detailed information about a specific package order.

    Args:
        order_id: The ID of the package order

    Returns:
        Detailed information about the order
get_scheduleB
    Get the full delivery schedule for an order.

    Args:
        order_id: The ID of the package order

    Returns:
        Formatted schedule showing all deliveries
get_orders_by_date_rangeC
    Get all deliveries within a specific date range.

    Args:
        order_id: The ID of the package order
        start_date: Start date in YYYY-MM-DD format (inclusive)
        end_date: End date in YYYY-MM-DD format (inclusive)

    Returns:
        List of deliveries within the date range
reschedule_deliveryB
    Reschedule a single delivery to a new date.

    Args:
        order_id: The ID of the package order
        group_id: The ID of the order group (delivery) to reschedule
        new_date: The new delivery date in YYYY-MM-DD format
        address_id: The address ID for delivery
        order_type: Either "LUNCH" or "DINNER"

    Returns:
        Success or failure message
bulk_rescheduleB
    Bulk reschedule all deliveries within a date range to new dates.

    Args:
        order_id: The ID of the package order
        start_date: Start of the date range to reschedule (YYYY-MM-DD)
        end_date: End of the date range to reschedule (YYYY-MM-DD)
        target_start_date: The new start date for rescheduled deliveries
        order_types: Optional - "LUNCH", "DINNER", or "LUNCH,DINNER"

    Returns:
        Summary of rescheduling results
get_available_addressesB
    Get available delivery addresses for an order.

    Args:
        order_id: The ID of the package order

    Returns:
        List of available addresses with their IDs
get_delivery_summaryB
    Get a summary of delivery statistics.

    Args:
        order_id: The ID of the package order

    Returns:
        Summary with total, remaining, completed counts by type
skip_dayA
    Skip deliveries on a specific date by moving them to the end of the schedule.

    Args:
        order_id: The ID of the package order
        skip_date: The date to skip (YYYY-MM-DD)
        order_types: Optional - "LUNCH", "DINNER", or "LUNCH,DINNER"

    Returns:
        Summary of skipped deliveries
hold_deliveriesB
    Hold (pause) deliveries for a date range.

    Args:
        order_id: The ID of the package order
        hold_start: Start of hold period (YYYY-MM-DD)
        hold_end: End of hold period (YYYY-MM-DD)
        order_types: Optional - "LUNCH", "DINNER", or "LUNCH,DINNER"

    Returns:
        Summary of held deliveries
change_addressB
    Change delivery address for specific deliveries.

    Args:
        order_id: The ID of the package order
        new_address_id: The new address ID to use
        date: Single date to change (YYYY-MM-DD)
        start_date: Start of date range (YYYY-MM-DD)
        end_date: End of date range (YYYY-MM-DD)
        order_types: Optional - "LUNCH", "DINNER", or "LUNCH,DINNER"

    Returns:
        Summary of address changes
get_available_restrictionsB
    Get all available dietary restrictions (pantangan) that can be set.

    Returns:
        List of available restrictions grouped by category
get_my_restrictionsA
    Get the current user's dietary restrictions (pantangan).

    Returns:
        List of the user's current dietary restrictions
update_restrictionsA
    Update the user's dietary restrictions (pantangan).

    Args:
        restriction_ids: Comma-separated list of restriction IDs to set.
                        Use empty string or omit to clear all restrictions.

    Available IDs:
        Protein: 1=No Udang, 2=No Ikan, 3=No Sapi, 13=No Cumi, 15=No Seafood
        Additional: 4=No Kecombrang, 7=No Sayur, 10=No Telur, 12=No Olahan Susu, 14=No Kacang
        Rasa: 5=No Pedas, 11=No Mayo

    Returns:
        Result of the update operation

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between bulk_reschedule and reschedule_delivery, as both handle rescheduling with different granularities. Tools like get_available_addresses and get_my_restrictions are clearly separate, but the rescheduling functions could cause confusion if not carefully described.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., get_order_details, update_restrictions, hold_deliveries). The naming is predictable and readable throughout the set, with no deviations in style.

Tool Count5/5

With 15 tools, the server is well-scoped for managing package orders, deliveries, and dietary restrictions in a food delivery context. Each tool serves a specific function, such as authentication, retrieval, scheduling, and updates, without appearing excessive or insufficient.

Completeness4/5

The toolset covers core CRUD operations for orders, deliveries, addresses, and restrictions, including authentication. Minor gaps exist, such as no tool for creating new orders or deleting/cancelling deliveries, but agents can likely work around these with the available scheduling and update tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources