Skip to main content
Glama
Sign In
Paxaver MCP Server

Paxaver MCP Server

Official
by Smartoire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Schedule Lunch Menu Item (Admin)

schedule_lunch_menu_item
Idempotent

Set a menu item as orderable on a chosen date, optionally capping available portions.

Instructions

ADMIN: Puts a restaurant menu item on the orderable menu for a given date, optionally capping portions. This only schedules the item - to retire it entirely use update_restaurant_menu_item (is_active) or archive_restaurant_menu_item. Requires pac_cordinator or lunch_cordinator role. WRITE - confirm with the user. Get IDs from list_school_restaurants and list_restaurant_menu_items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "restaurant_id": "<restaurant_id>",
      "menu_item_id": "<menu_item_id>",
      "menu_date": "<menu_date>"
    },
    "name": "schedule_lunch_menu_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
menu_dateYesDate the item is orderable, YYYY-MM-DD
menu_item_idYesMenu item ID - from list_restaurant_menu_items
available_qtyNoMaximum portions for the day; omit for unlimited
restaurant_idYesRestaurant ID - from list_school_restaurants

Output Schema

NameRequiredDescriptionDefault
idNoDaily-menu entry ID
menuDateNoDate the item is orderable, YYYY-MM-DD
menuItemIdNoMenu item scheduled
availableQtyNoPortion cap for the day; null means unlimited

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already convey write/non-read, non-destructive, and idempotent behavior. The description adds value by specifying the role requirement, the 'WRITE - confirm with the user' confirmation protocol, and the scope limitation ('This only schedules the item'). No contradiction with annotations exists.

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 compact but information-dense: admin marker, action, scope limitation, sibling alternative, role requirement, confirmation prompt, and ID sources all appear in a few sentences. Key operational facts are front-loaded and every sentence earns its place.

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 an output schema present and annotations covering idempotency/safety, the description supplies the remaining necessary context: role, confirmation, retirement alternatives, and ID source guidance. Nothing critical for selecting and invoking this tool is missing, though it could explicitly mention date format, but that is already in the schema.

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 100%, so the baseline is 3. The description adds useful context by pointing to the source list tools for restaurant_id and menu_item_id, and by explaining available_qty as 'optionally capping portions' / 'omit for unlimited', which reinforces the schema semantics.

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 states a specific verb and resource: 'Puts a restaurant menu item on the orderable menu for a given date'. It explicitly distinguishes this action from retiring an item via update_restaurant_menu_item or archive_restaurant_menu_item, which clearly separates it from sibling tools.

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?

The description provides when-not guidance by naming alternatives for retirement, states the required roles ('Requires pac_cordinator or lunch_cordinator role'), and instructs the agent to get IDs from list_school_restaurants and list_restaurant_menu_items. This leaves no ambiguity about when to use this tool.

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